Mike Harris' Testing and Quality Blog
When I automate a test I create a clean starting position for each test so that the automated tests can run concurrently. “The establishment of a known-good starting position for the test before it is run, and its re-establishment at its conclusion, is vital to avoid cross-test dependencies”[1]. Re-establishing the start position of the test …
Continue reading “There are advantages to using the API to tear down automated end-to-end tests”
“A regular expression defines a set of one or more strings of characters” [1]. Regular expressions (regex) can be used when developing automated tests, for example, by passing a regular expression as a parameter. If you have not used a regular expression before the MDN Web docs are a good place to start learning about …
Continue reading “Regular expressions can help you to do more with your automated tests”
A linter is a static analysis tool that scans source files and reports warnings and errors for the code it scans. I use a linter on the test automation code that I write. The linter tests the code I write without running the code. Here are ten reasons to use a linter on your test …
Continue reading “Ten reasons why you should lint your test automation code”
Each project has different requirements, and each set of requirements makes its own demands on ‘quality’. On every project I work on, I find it useful to interpret ‘quality’ in more than one way. Interpreting quality is more helpful than defining it. A definition is definitive whereas you can have many interpretations. It is useful …
Continue reading “Interpreting ‘quality’ in more than one way helps me uncover issues”
One of the challenges in writing automated tests is to have a low maintenance cost of the tests. Creating a library of functions in a Page Object Model helps because the test can reuse the functions in the library. Typescript generic functions within my Playwright Page Object Model also help me, in some situations, to …
Continue reading “Generic functions help me to reduce the amount of Playwright test automation code”
Sometimes testers are asked ‘why does testing take so long?’ The question should not make testers feel defensive. We should always be looking to improve our test process. Testers can use a technique from Toyota to answer the question and improve our process. Testers want their testing to flow easily from one task to the …
Yesterday I was using a testing tool and it had an outage. Today I was automating a test when a third party had an outage and delayed my test automation. Even the third party’s Status page was not functioning. Social media was full of people complaining about the outage. Outages impacted two consecutive days of …
There are times when automating a test in Playwright that the test needs to wait because the test will flake if it does not wait for something such as an event. It can be, for example, that you are waiting for a navigation to complete. Tests can be made to wait with a ‘wait’ for …
Continue reading “Make your Playwright tests run faster by using the Playwright API to wait”
Test analysts, test engineers, test leads and test managers need to understand customers so that our testing includes using the product as the customer uses it. To do this we need to learn how customers use the product by meeting the customer and seeing how they use it. Mr Fuji Cho, the former President of …
Learning from discussions originating from code reviews is helping me create a pack of automated tests using TypeScript and Playwright. I have been developing a pack of Playwright tests with a Page Object Model. A simplified example of a page in the Page Object Model looked something like this: A simplified example of a test: …
Continue reading “Use code reviews to have discussions about your test automation code”
Testers are learning all the time. I have been reading John Dues’ new book Win-Win: W. Edwards Deming, the System of Profound Knowledge, and the Science of Improving Schools with the Profound Deming Book Club and have gained insights into different ways of learning. “Moving from planning to doing is deductive learning and moving from …
Continue reading “Two ways of learning that benefit testing”
An end-to-end test pack needs to run quickly so that it does not slow developers, and at the same time provide useful feedback to the developers. This makes deciding which categories of tests to include in the test pack challenging. A ten-minute video from Russ Ackoff has helped me better understand my decisions on one …
Continue reading “How do you decide which tests to automate?”
I have been reading John A. Dues’ new book Win-Win W. Edwards Deming, the System of Profound Knowledge, and the Science of Improving Schools with the Deming Profound Book Club. John Dues uses an equation to describe who is responsible for student performance[1]. This equation works as a useful analogy to describe who is responsible …
Continue reading “Who is responsible for quality? Is it the tester, or the team?”
Sometimes testers are asked how long it will take to automate a batch of tests. Planning how long your test automation should be simple, however, the plan will have missed some requirements. There are three types of requirements[1]: “We will never understand all the requirements of a story ahead of time”[2], this applies to test …
I am using Playwright to automate end-to-end tests, and have started to complement my Playwright tests with Chromatic tests. The Playwright tests are really useful, but each test needs to run through several steps to create a scenario I want to test. Creating a Playwright test for each input variation for each part of the …
Continue reading “Do Chromatic tests complement Playwright tests?”
TestAndAnalysis