A Practical Approach to Early-Cycle QA Test Automation
Everyone knows that a large body of automated unit tests for classes, subsystems, and frameworks adds to overall code quality. However, the "burden" of unit test automation is frequently placed squarely on the shoulders of developers because of the perception that only a developer can write a unit test. Since QA personnel typically test from the user interface-and usually have to wait until later in the development cycle for the availability of that interface-they're often left to scramble at the end of the cycle to get their testing done. Michael Silverstein reveals a model for early-cycle collaboration between developers and testers where testers augment the developers' unit testing activities without adding additional process overhead.
Agile + DevOps West
The Latest in Agile and DevOps
Software Testing Conference in Anaheim & Online
Agile + DevOps East
The Conference for Agile and DevOps Professionals
Software Testing Conference in Orlando & Online