The fourth industrial revolution – the digital revolution – has strong requirements for companies operating under strict business regulations. Particularly, in the healthcare sector, companies must spend great efforts to…
Test Categories When it comes to Test Strategy for any reasonable sized / complex product, one aspect would always be there – the categories of tests that would be created,…
I’m a Developer Advocate and one of the things I love most about my role is that I travel all of over the world – meeting and consulting with engineering…
Visual UI testing is more than just testing your app on Desktop browsers and Mobile emulators. In fact, you can do more with Visual UI testing to run your tests…
What is a design system? Who would use it, and for what benefit? In May 2020, Applitools had the pleasure of hosting Tyler Krupicka from Intuit for an hour-long webinar…
Ready For a Challenge? If you are up for a challenge and enjoy learning new skills, join the world’s best quality engineers between now until June 30th to compete in the…
What does it take to add UI tests in your CICD pipelines? On March 12, Angie Jones, Senior Developer Advocate at Applitools, sat down with Jessica Deen, Senior Cloud Advocate…
If you run continuous deployment today, you need high-performance testing. You know the key takeaway shared by our guest presenter, Priyanka Halder: test speed matters.
Elite teams add CI test automation early – and not full development database tests, but simple unit tests that can run in less than 10 minutes and validate code that has been written.
How do you bridge the gap between quality engineering and product management? In October 2019, Evan Wiley from Capital One presented on this topic for an Applitools webinar. Evan introduced…
You can easily integrate visual UI tests into your CI/CD workflow. Simply add an additional task in the workflow to run the visual UI tests. Typically, the CI Provider runs the automated tests and sends the results to the Visual Testing Provider. The Visual Testing Provider analyzes the testing results and reports them back to the SCRM on that specific PR.
If developer-check-in-to-prod works for your organization, then you should do it…provided you understand the risk. This risk manifests in two big buckets: cost of change and cost of failure.
