Be the first to like this
The concept of continuous integration (CI) and continuous delivery (CD) based on daily builds, test automation and automated deployment, is becoming popular and widely used in the industry. Automation efforts support both quality improvements and agility acceleration. Recently the scope of test automation has expanded, system-level testing is now automated and included in continuous daily builds.
Before the automation era, system tests were only executed on build artefacts once all implementation was completed. However, system testing is now conducted in parallel with implementation of product code as regression tests. This continuous system test practice allows the development team to lower the cost of bug fixes.
On the other hand, the concept of system testing is not well understood from the perspective of traditional QA. For example the bug curve is smoothly convergent in traditional QA, but it is rapidly convergent in a continuous system test environment.
In this report, source code, bugs and implementation metrics are analyzed for better understanding of continuous system test concepts.
Profile: DevOps engineer in Rakuten inc. He started his career as a search engine developer, then developed a system test automation framework for non-functional tests including resilience testing and search quality testing. Currently he leads a test automation team and DevOps team for expanding the concept of Continuous System Test in the organization.