Conferences are often filled with software testing success stories. It can be just as enriching and much more fun to hear about how not to do something. This lightning talk is all about software testing gone wrong.
Software Testing Videos and Tutorials: Load Testing, Unit Testing, Functional Testing
Users care as much about how your service performs as they do what job it helps them accomplish. This is why performance is imperative and performance testing a must. So why do we still see so many 503 errors and slow apps? The answer is empathy, a lack thereof. Performance is the most tangible element of “non-functional” quality criteria we regularly ignore until it’s too late.
xUnit.net is an open source unit testing tool for the .NET Framework. Written by the original inventor of NUnit v2, xUnit.net is the latest technology for unit testing C#, F#, VB.NET and other .NET languages. xUnit.net works with ReSharper, CodeRush, TestDriven.NET and Xamarin.
This talk demonstrates to participants how they can use HTTP request libraries and WebDriver in harmony. A common pattern that Automator’s fall into is trying to execute every action of a test via the UI, from logging in, creating required data, navigating to that specific data and then running assertions on it before logging out. This can lead to tests that are slow to run and likely to break due to the reliance on many Web elements.
Software testing is today a crucial part of software development, but if it comes to good programming practices a lot of teams have some issues to create sustainable and maintainable tests. Learning the usage of a testing tool is often not enough for writing those. It is also necessary to create a framework which abstracts the different concerns.
Spock is a Groovy-based open source testing and specification framework for Java and Groovy applications that makes writing tests fun again. We can write beautiful and highly expressive tests for Java applications because of its domain-specific language (DSL) and all the power that Groovy provides us.
There are a lot of examples on the web on how to introduce good agile testing and architectural patterns when you are starting a new software development project. In reality, even on newer projects, you are more often working in a less than ideal state.