Continuous Integration is a software development practice where members of a team integrate their work frequently; usually each person integrates at least daily – leading to multiple integrations per day. Each integration is verified by an (preferably) automated build (including test) to detect integration errors as quickly as possible. This approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly
How it helps…
- Greatest and most wide ranging benefit of Continuous Integration is Reduced Risk
- CIT completely eliminates the blind spot ‘integration in a long and unpredictable process ‘
- At all times we know what works, what doesn’t and what are the outstanding bugs in our system
- CIT makes it dramatically easier to find and remove defects
- Helps get rid of ‘Broken Windows Syndrome’
- Removes one of the biggest barriers to frequent deployment
- Allows users to get new features more rapidly
- Gives more rapid feedback on those features
- Helps break down the barriers between customers and development
CIT Process Methodology
Continuous Integration Testing is not an independent testing process. It’s a process performed as frequent as the code merge is done and is an end to end process that involves Release Management, Configuration Management, Test Management (environment / data / test cases / automation of fact checking) and Defect Management.
Continuous Integration Testing Approach
Step wise Testing approach that we normally take. Your project needs could be different. Draw your approach for your context!! Percentage Level of Automation for the fact checking can vary a whole lot, so be prepared to take that into account.