Continuous Integration and Testing
The biggest waste in software is created from waiting for software as it moves from one stage to another: waiting to code, waiting to test, waiting to deploy. Reducing or eliminating these waits leads to faster iterations, which is the key to success.
The integration phase in a typical software development life cycle (SDLC) is the most complex and has stressed many developers and quality control people; it’s an ‘event’ that may consume a good amount of time and resources. Big products (sizes) and complex services (domains) have demanded integrations with varying levels of complexity and largenumbers of modules and/or functions into a system. This process could take days or weeks and sometimes months to complete. So, when do we check if an old product or service is working fine, or if the new product or service with changes is working okay? Is it when everyone is done with his or her integration? This approach is being challenged and most of the subject matter experts agree: The answer as NO!
Continuous integration (CI) and testing practically would mean one proactive extra step toward continuous quality control. It is a practice that will lead us to better quality control (QC) and quality assurance (QA) right from our first thought of integration. Theoretically, and in simple terms, it means to integrate every couple of hours or sooner and
Please log in or sign up below to read the rest of the article.