The Latest

Being a test manager is more than just being the boss. Sure, there is direction to set, issues to address, hiring, performance reviews, and status updates.

Many agile teams rework previously deployed stories, even after plenty of in-sprint testing. Well groomed, refined, stories framed with typical, alternate and error scenarios, gracefully described in well formed gherkin, continue to encounter all sorts of bugs.

You'll learn character development techniques to build customer personas, strategies for plotting a "story" end to end, and tips for projecting potential obstacles.

Noha Gomaa champions "testing as a service" to project teams, helping them implement testing in different lifecycle models for major infrastructure transformations and highly custom, product-specific projects. Noha will share how this service model can work in any organization.

Part 2: Come learn how to put together the advanced concepts of an API test in a framework that is scalable, robust, and easy to read and eliminates the brittleness in your checks.

One of the lines in the Agile Manifesto is "Working software over comprehensive documentation." This doesn't mean that no documentation is produced, but instead that only documentation that brings value to the team and the customer should be created.

Too often quality is identified as solely owned by the quality assurance team. By taking a broader approach to roles, tools, and ideology, you can restructure your vision of how to provide rapid, frequent releases that empower all delivery team members.