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.
Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing
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.
Matt Wynne, co-founder of Cucumber, delivers a short webinar presentation on 10 easy ways to fail at Behavior-Driven Development (BDD). Many organizations desperately want to enjoy the benefits of practicing Agile testing BDD, yet set themselves up for failure.
There is a lot of talk around software testing - who will do it, when it needs to happen, boxes it needs to fit in — yet not enough on the actual testing. This webinar explores one problem in a demo setting using an exploratory testing approach. This means live testing (and live coding) to figure out the options to get a test program covered – for code coverage, for spec coverage and for risk coverage.