I took a risk with Cypress - and I’m glad I did.
Writing and maintaining tests is a necessity if you want confidence in your product when it ships, but it can be a frustrating experience. Cypress is a Javascript frontend test automation platform. Despite Cypress being a relative newcomer, it will likely replace Selenium Webdriver as the de facto standard.
Early in its inception, I fell in love with Cypress, teaching and promoting Cypress in the community in addition to using it in my day job. The commitment was risky. Today’s hot JavaScript framework could tomorrow’s old news.
More recently, I was invited to the Cypress Ambassador program, launched another workshop and started iheartjs - iheartjs.dev the iheartjs YouTube channel where I live-streamed the workshop and soon, a newsletter. To say the least, I've gone “all-in”.
Today, I’m attending the TestJS Summit and not only am I impressed by all the speakers so far, I’m blown away by all the love for Cypress! I never needed the community’s overwhelming approval to back a solid product, but today my commitment has been truly validated and I couldn’t help but take to Twitter:
@bromann said at @TestJSSummit that he's "rooting for @Cypress_io" to "push the boundaries of automation and really provide so much value for the developer persona" 🙌 https://t.co/gs9bfM0SUY
— Mike @iheartjs.dev (@mccataldo) January 28, 2021
♥️ our users https://t.co/vBnSyyvfcw
— Gleb Bahmutov (@bahmutov) January 28, 2021
Gleb Bahmotov also shared his excitement:
Nice! @techgirl1908 showing visual testing with @Applitools @Cypress_io SDK @TestJSSummit pic.twitter.com/At1YDqgpCH
— Gleb Bahmutov (@bahmutov) January 28, 2021
I’m so grateful for the Cypress community and even the JavaScript community as a whole. I have even greater confidence going forward which means more content for you in the near future!