Content in the Videos category
Johanna Rothman first started managing a software testing group in 1988. Since then, she managed software testers, coached testers or coached project managers and managers in what they should—and should not—expect from testers.
Writing tests looks simple and every kid could write few lines of JUnit code. Writing valuable tests is more challenging. Everyone have seen (or written himself!) tests, which are hard to understand, hard to maintain, and do not verify anything really important (or maybe they do, but it is too hard to deduce)!
By working together to create the set of tests and then determining where that testing belongs, we can increase efficiency, reliability and reduce debugging time for failures in the future.
Tools like Selenium make writing automated browser tests dead easy. Many teams never look further than this, and are satisfied with just replacing their laborious manual testing efforts with reliable Selenium scripts. They’ve missed a big opportunity.
This presentation shows how to easily go from user stories to automated integration tests that themselves read like user stories. You can accomplish this by using custom domain-specific languages (DSL).
Testing strategies are well understood and established in traditional Object Oriented and/or functional settings. The same is not true for asynchronous, event-driven paradigms such as the actor model, in which the timing and execution context of assertions is important and temporal relations between generated events become test objectives.
A detailed guide to creating a mature and paralellizable automated software testing suite. This talk will cover things such as data independence, atomic tests, state generation, testing oriented pages. It includes sample code, demos and funny cat memes.
Learn how to perform functional testing on JSF applications with Arquillian and Selenium. In modern development environments, it’s a must to include testing of Web applications as a standard part of the development lifecycle. Such tests can also be used as acceptance criteria in enterprise projects. Although full automation is possible, it is considered to be very expensive. As a result, in projects where testing is included as part of the project plan, it is also often the first requirement cut when the project schedule begins to slip.
Daniel Wagner-Hall set up and maintains the continuous integration server for the Selenium project; every check in runs several hundred tests in 30+ browser/version/OS combinations, totaling 3.5 days of tests every day!