Related Content
3 Reasons Testers Shouldn’t Be Afraid of AI How do testers contribute in agile? DevOps? Should testing tools and automation replace most things that manual testers do? At this point, testers are almost required to hold their breath whenever people start talking about new trends, and artificial intelligence is no different. |
||
Elevate Code Quality by Integrating Testing and Development Pair programming generally involves two programmers working on a single change from start to finish. You can augment this pattern by adding a test specialist, so you can test-drive feature changes first and the tester can ask questions and guide test and code design. What you get is quality built in from the start. |
||
Testing in a Pair Programming Environment If a development team does pair programming, where does testing fit in? You don't have to wait until the programming is done—testers can be part of the whole process, from code design to reviewing changes to production. Pair programming plus a good automation strategy mean quality is built in throughout development. |
||
DevOps and Test Automation: You Missed a Spot The key success factor for DevOps is the commitment from teams, managers, and other stakeholders. There should be agreement that tests and their automation can be important re-usable products, which need attention and cooperation to be able to support approaches like DevOps effectively. |
||
What Working at Netflix Is Like The Netflix team has to be dynamic in order to move as quickly as the demand of its audience. Because of that, the company only hires senior engineers, avoids actually sticking to process whenever possible, encourages a great deal of employee freedom, and even pushes budgets to the side. |
||
Government’s Federal Source Code Policy Mandates 20 Percent Open Source In an attempt to reduce duplicating government IT and software resources, the US federal government recently announced the “Federal Source Code” policy, which requires new custom-developed source code used by federal agencies to be made available for sharing and reuse government-wide. |
||
The Basis of Test-Driven Development: Writing Effective Test Cases Too often, test-driven development still initially focuses on coding aspects, not testing. The first step in a test-driven approach has to be writing effective tests. It's not enough to simply ensure good coverage; effective tests should also confirm that decisions made in the code work correctly. |
||
Go-Live Lessons: The Path from Software Development to Production On systems integration projects where a vendor is building or configuring a system for a client, you sometimes cross the canyon from development to production and maintenance in several smaller bounds rather than one big leap. A warranty period after go-live can help stakeholders confidently monitor quality. |