|
Logic and Software Testing Formal logic is what runs computers, but it is only a part of the logic used by a software tester. In this installment of his ongoing series on philosophy and software testing, Rick Scott explains.
|
|
|
As Testers, How Do We Know What We Know? Software testing is a process of acquiring knowledge about software. But, how do we know what we know or how to acquire knowledge? Rick Scott shows what the study of epistemology means for testers.
|
|
|
Testing Metaphysics Metaphysics will help you investigate your purpose in life, separate the real from the imaginary, and argue about whether or not humans have free will. According to Rick Scott, it can also help you become a better software tester. As the foundation of philosophy, metaphysics deals with identifying the fundamental assumptions we make about the world and seeing how well they hold up to close scrutiny.
|
|
|
Put a Load on It: Combining Load and Functional Testing Typically, industry software testing practice is to separate load testing from functional testing. Different teams with different skills and expertise do their testing at different times and each evaluates the results against its own criteria. We don’t always need to do this in pre-release testing. When time to market is more important than strict accuracy the pilot system can become the load test system while the test team does routine checks during pilot to mitigate risk.
|
|
|
My Experience with Test-Driven Development Vinay Krishna explains why agile development includes testing and coding concurrently, which is also what test-driven development emphasizes. The transformation from coder to developer to tester is needed in all agile software development projects.
|
|
|
From One Expert to Another: James Bach In this installment of From One Expert to Another, Jon Bach uses a 20 Questions approach to interview his brother, James Bach, about his reputation, his work as a tester and consultant, his thoughts on the global testing community, and more.
|
|
|
Transitioning to Agile Testing Your developers are already working feature-by-feature in iterations, but your testers are stuck with manual tests. How do you make the leap to agile testing when the nature of agile's iterative releases challenges testers to test working segments of a product instead of the complete package? In this column, Johanna Rothman explains that the key challenge resides in bringing the whole team together to work towards the completion of an iteration. Only then will the testers—and the entire team—know how to transition to agile.
|
|
|
Agile Performance Testing Approaching performance testing with a rigid plan and narrow specialization often leads to testers' missing performance problems or to prolonged performance troubleshooting. By making the process more agile, the efficiency of performance testing increases significantly—and that extra effort usually pays off multi-fold, even before the end of performance testing.
|
|
|
A Word with the Wise: Assessment First with David Dang David Dang, a senior practice manager for Questcon Technologies, explains why you need think about the tool you select. According to Dang, the assessment of the project and its goals should always come first in test automation projects, otherwise, you risk maintainability issues down the road.
|
|
|
The Trouble with Tracing: Traceability Dissected Traceability! Some crave it. others cringe at the very mention of it. For hardcore configuration managers and requirements and systems engineers, it is a fundamental commandment of “responsible” software development. For many hardcore agilists and other developers, the very word evokes a strong “gag” reflex, along with feelings of pain and frustration. Traceability requires work and discipline! So how does traceability add value to our business and how can we make it easier?
|
|