Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
James Waldrop of Twitter discusses the tools, process and philosophy that goes into performance testing at Twitter. Particular emphasis will be placed on the Iago open source load testing library, which he wrote to enable Twitter’s engineering teams to perform load tests before deploying code to production. This presentation dives into implementation details of some of these tests (including source code) and how complicating factors such as OAuth and arbitrary Thrift protocols are managed. Video producer: https://developers.google.com/google-test-automation-conference/ Slides: http://goo.gl/9VY2b
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.
Testable JavaScript is a process. Whether starting with a blank slate or an already implemented application (or somewhere in-between) being able to test your JavaScript code simply, cleanly, and effectively is a necessary feature. Code that cannot be tested will be rewritten.
When software developers and software testers work together to create the set of tests and then determining where that testing belongs, they 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.
