Tutorials and resources on how to apply test automation in software testing
One of the most widely touted drawbacks of the automated tests is that they work in strictly bounded context. They can only detect problems for which they are specifically programmed. The standard automated test has a bunch of assertions in the last step. By definition, an automated test cannot detect an ‘unknown’ problem. Because of their narrow focus, the automated tests are occasionally compared to dumb robots. It takes a lot of time and effort to write and support them however their return on investment is still marginal.
Different people from the software testing field can have completely opposing opinions about the process of test automation. Sometimes it happens that after a while, the initial expectations and hopes of this substantially costly investment are not justified at all. In simple words, test automation does not bring the expected profits. In this article, we will try to understand why such situations happen and how to avoid the most common mistakes.
Applications are one of the most exposed parts or any organization, but most companies fall short on knowing how and what to monitor within them. In this presentation, Kevin Johnson of Secure Ideas uses his background as both a software developer and a penetration tester to show attendees how to determine these methods.
Viktor Slavchev shares some hindsight about an API testing project. API is one of the areas where it makes sense to invest in test automation, because it is an interface that is consumed by code or by an application. So, it fits perfectly the description of easy to test with code application. However, Viktor Slavchev is amazed how little information is available about API testing basics.
Acceptance tests are defined in this book as the test created by the customer in collaboration with the developer and the tester prior to implementation. They are not the traditional user acceptance tests performed after implementation. Although acceptance tests can be used at different development stages, Ken Pugh proposes mainly in this book an approach where all project stakeholders will collaborate to create tests that validate business requirements.
Junit 5 is a big step for the world of unit testing for Android apps. This is a new very flexible open source testing framework, based on many years of experiences with Junit 4. At the sporttotal company, we use Junit 5 for our Android unit tests and it changed the way we write our tests. Hard for us to imagine living without features like @Nested. Other features we ignored as those are more leaning towards Java and are solved already by Kotlin or other Kotlin libraries. And some features are even breaking changes.
It is difficult to maintain and evolve software systems and applications without some automated testing tools that help you making sure the changes are not breaking the existing features. This white paper from Indium Software presents you the best regression testing tools available in 2019.
