Many organizations are currently using an Agile approach to software development. In this context, small teams are recommended with an emphasis on collaboration between team members and cross-functional people. In this blog post, Rob Lambert discusses the actual skills of software testers and how they go beyond software testing, producing what is call a “t-shaped tester”.
Do you want to learn how to coach software testers to be skilled at what they do, using a systematic approach? Coaching, unlike training puts the student at the centre of the session. You coach on what the student wants to learn , with the goal of empowering and motivating the student. While these are ultimately the responsibility of the student, there are ways a coach can help a student feel more empowered. Learn how to guide a student through a coaching task, helping them to feel challenged and motivated to continue to discover more.
Writing and keeping up to date documentation in software development projects has always been a problem. In this blog post, Jim Bird discusses the idea of using automated tests to document a software system. He also ask the questions: what do tests document? who will find this documentation useful?
Populating systems under test with data is often done by cleaning and inserting data directly into databases using SQL scripts. Whilst this technique is simple, it can have several drawbacks for automated tests.
Answering an article saying that you cannot use exploratory testing in Agile, Huib Schoots tries to explain what exploratory testing is and why it is suitable to perform this activity in an Agile context.
Behavior-Driven Development (BDD9 and Acceptance Testing are heavily intertwined and in many aspects are one and the same. Both focus on starting at the outer layers of your application by concentrating on what matter to users; behavior.
Pex is a Visual Studio 2010 Power Tools that help Unit Testing .NET applications. Pex automatically generates test suites with high code coverage. Right from the Visual Studio code editor, Pex finds interesting input-output values of your methods, which you can save as a small test suite with high code coverage. Microsoft Code Digger is a Visual Studio 2012 that analyzes possible execution paths through your .NET code. The result is a table where each row shows a unique behavior of your code. The table helps you understand the behavior of the code, and it may also uncover hidden bugs.
Copyright © 2009-2026 Software Testing Magazine by Martinig & Associates