Test automation
Playwright is a UI automation test tool that supports Chrome, Edge, Firefox and Safari browsers. It was released in January 2020, has 74.7k stars on GitHub, and is fully open sourced and maintained by Microsoft. Playwright uses the Chrome DevTools Protocol, Firefox Remote Debug Protocol & WebKit Debug Protocol to…
Nightwatch is a UI automation test tool that supports Chrome, Edge, Firefox and Safari browsers. It was released in January 2014, has 11.3k stars on GitHub, and is fully open sourced and maintained by BrowserStack. Nightwatch uses the WebDriver protocol to perform the browser automation tasks, and can be used…
Cypress is a UI automation test tool that supports Chrome, Edge, and Firefox browsers, has a GUI test runner to aid in debugging. It was released in September 2017, has 48.7k stars on GitHub, and is maintained by Cypress. Cypress tests run inside the JavaScript engine of the browser, however…
In the post on UI testing with Selenium – record and refactor, the tests ran locally using Chrome. They were subsequently modified to run faster by running Selenium tests in parallel. For tests to be actually useful in the real world, they need to run on multiple browsers, on different…
In the posting on Selenium Testing, the tests run one after the other. For very small tests this is usually fine, but as the test pack increases in size, it will be advantageous to decrease the test execution time by running the tests in parallel. JUnit 5 options The JUnit…
Capturing screenshots of the browser via Selenium is fairly easy to achieve (see a sample method here), but triggering a screenshot only when a test fails is useful for both debugging and result reporting, however this requires a little more code and some modifications to your tests. JUnit5 For Junit5,…
Developing tests for web based front end applications can be a time consuming task – once you have identified the test cases you wish to automate, you have to examine the UI components of the application and determine the best locators to use for each element.Once the initial prototype tests…
In an earlier post we looked at Kafka and got hands on with creating topics, and producing and consuming messages. However, the basic tools are limited and only simple manual testing would be possible. Ideally we want to write automated tests, as these are repeatable and allow us to use…
Following on from GWT syntax and BDD, this post investigates how a Cucumber test is structured, and starts to explore some of the features of Cucumber and Gherkin syntax (the keywords Cucumber uses to execute the tests) The anatomy of a Cucumber test Cucumber tests are a lot more complex…
As mentioned in Getting started with API’s, tools like Postman are useful for hands-on testing of API’s, but automated API testing is better performed in code and there are several frameworks available to support this, with Rest Assured being one of the most widely used. A test endpoint Obviously to…
