QA testing should do these 4 things: Make sure software works Most of the time, test automation is really only doing #1 — making sure that it works, by navigating around the application, and performing basic functions. This is ok. This is what automation is good at. But you also need to do other things.…

I tried to get ChatGPT to teach me a simple coding challenge today… With a little help (from me), it got the following Python code: I asked ChatGPT why when I run the code I get a different number (17710): Here, it fails to stop before 10000. But still thinks it gets 19683 (instead of…

Why do you need a test framework? Isn’t automation enough? A test framework helps to organize test code, making it easier to maintain, faster to add new tests, and easier to track down issues.

Testers aren’t developers. At least most of them aren’t. Or they didn’t start out that way. But now you have a bunch of automated tests, an organically grown test framework, and assorted tools for managing test data and environments. Your developers won’t touch the tests. They’re only kept running by a miracle — and by…

Your testers have verified that everything works as expected. Your developers have fixed all the bugs that your testers have found. Your roadmap looks great and your’e ready to release ahead of schedule. But then there’s the final hurdle: user acceptance testing. Apart from a few typos, and minor usability issues that can be addressed…

Test Automation makes testing faster and easier. It frees up developer time to focus on delivering features. It gives assurance to DevOps and SRE teams that deployments and releases are successful. And it enables testers to spend more time doing high value exploratory testing and finding bugs. But if there are still manual steps in…

You can run your test automation locally, and may even have set up a Selenium Grid and gotten your tests running as part of a Continuous Delivery pipeline using Jenkins or Github Actions. But tests are still slow. And you’re only testing on a single browser (Chrome, most likely.) You need to run tests in…

Has your test automation grown ad-hoc into a complex mess? Slow test runs, flaky tests, high maintenance costs, low visibility, and difficulty training testers to use your test framework are signs that you could use a test architecture overhaul. Let’s talk about what you can do to bring back fast, reliable test results. One Shore…