Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
Most research on Agile Testing and QA have requirements on highly automated testing/CI and an Agile or Scrum project-management structure. How can we iterate towards a more Agile testing process, with all the benefits that entails, when some of the common requirements are missing or undesirable in the near-term?
How good are your test cases? Maybe they are good, or maybe you need to add some new ones. How to tell? You can measure things like code coverage to check if some parts of your code were not executed. Still, this does not tell you anything about the quality of your assertions and your software testing results. In the extreme case, a test suite with no assertions might still achieve 100% code coverage, although being of questionable value.
This presentation will show you why the testing pyramid need to be very wide. You will understand why this is an absolute necessity if all possible paths through the application should be tested. In other words, let me show you why your tests must be very shallow.
Although Behavior Driven Development has been existing for over 10 years, the methodology hasn’t yet been very popular in the Java world. One reason for this are the existing BDD tools for Java that are cumbersome for developers to use and require a lot of maintenance.
Creating a comprehensive testing suite is imperative to success in the mobile market to ensure your app is of the highest quality with each and every release. Unit tests can only test your core business logic. How can you ensure your user interface is bulletproof and regression free on four versions of iOS on 20 devices or eight versions of android on over 18,000 device models? This is where creating automated user interface testing for mobile apps comes in.
This talk introduces the core accessibility affordances on the Android platform and illustrate some common developer pitfalls related to accessibility. You’ll learn about the new Android Accessibility Test Framework and its integration into the Espresso and Robolectric testing frameworks. Finally, you’ll learn how easy it is to add automated accessibility checking to your your existing Android project tests.
Almost every manual QA started with Selenium IDE or at least tried it at some point, and the retention rate is close to 0. This talk depicts the challenges that Test Automation Developers face. We categorize the challenges, name them, and see the skill set required to overcome the difficulties.
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates