Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
There is a lot of talk in modern software testing teams about experimentation. Classically an experiment is a very structured series of activities designed to find something out. Sounds a lot like software testing and is in direct alignment with the concepts around Test-Driven Development (TDD), Behavior-Driven Development (BDD) and Acceptance Test-Driven Development (ATDD). This video discusses how to design testing experiments that are valuable and provide the right insights to the right people, at the right time.
There is a value in writing tests and there is also a cost. The currency is time. The trade-offs are difficult to evaluate in software testing because cost and value are often seen by different people. The writer of the test bears much of the short term cost while long term benefits and cost are borne by the rest of the team.
DevOps is based on continuous delivery and anything that breaks the continuity is a bottleneck. While Agile and DevOps have become common terms in Development and Testing organizations, manual build and deployment processes are still causing problems along with integration and testing.
The evolution of software from a simple application running in an isolated system to a multi-node solution in a network and now to geographically distributed cloud solution with hundreds or thousands of nodes, has brought about its own challenges in terms of testing. Testing strategies which works well in one model is not really applicable to others. While many of the tests for a cloud hosted solution can be done by replicating a subset of the actual production environment, some test to be effective need a production like environment.
Learn about the effectiveness of coverage as a technique for evaluating quality of test suite. This presentation shows the utility of coverage by considering its correlation with mutation score, and also shows that coverage is a significant defense against bugs. It also critiques the effectiveness of mutation score as a criteria for test suite quality.
Probably there is no Java developer in the world who writes tests and haven’t heard about Mockito. That most popular mocking framework for Java will be celebrating its 10th birthday soon. However, I don’t plan to brood the history. At the end of 2016 the new and shiny Mockito 2 has been released.
James Bach defines Exploratory Testing as “simultaneous learning, test design, and test execution. In other words, exploratory testing is any testing to the extent that the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests.”
