Unlike normal web apps, PWA poses its own unique challenges that test engineers and automation engineers must pay attention to. This article discusses these unique testing requirements of PWA and how to approach them.
The question might sound mundane and the answer seems obvious but many automation engineers keep asking it again and again. So let's get to the bottom of it. Sure you can but it's not recommended.
If the UI of your web, desktop, or mobile app is not ready, what should you do? Sitting around waiting idly is of course not an option. The good news is as a software automation engineer, you can start working on many things.
The more automation the better. Automate once and run forever. Lack of preparation for provisioning and managing test environments. These are the three most common misconceptions about software test automation.
Free open-source automation frameworks are not actually zero cost. Their costs are just hidden out of sight. And we still have to pay somehow. This article discusses the merits of BUILD versus BUY when it comes to picking your Automation Framework.
Cypress has its own unique approach to web automation and there are good reasons they chose to approach it that way
Test Automation framework should meet such as supported automation platforms (desktop, web or mobile?), usability, maintainability, stability, ease of debugging test failures, ease of integrating test automation into a CI/CD pipeline, first-class Docker support, budget/pricing, etc.