Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
More and more organizations build test automation frameworks based on the WebDriver and Appium tools to perform software testing their web and mobile projects. A big part of why there are so many flaky tests is that we don’t treat our tests as production code. Moreover, we don’t treat our framework as a product.
It doesn’t matter if you are developing software with Java, .NET, PHP or another language. If you need to do performance testing – it will be a challenging task, especially nowadays with microservices architectures, clusters and very complex systems. This presentation addresses the most common pitfalls of performance tests. The presenter shares his experience gained through demanding experiments and quite often frustrating failures.
Running more than 5000 automated system tests on a deployed application with outgoing connections to about 25 other systems, each with their own dependencies, where test data is complex and needs to be in-sync, is a great challenge. Doing it every night, year after year, with the requirement to fail only on the event of actual errors in the application under test, is a nightmare.
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.
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.
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.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates