Continuous Testing in agile (CT)

Posted by
While giving an overview of Continuous testing it is stated that, the process of performing tests for the software deliverance and that to achieve the suitable results regarding the new release.
The next part is Continuous Deployment and is described as the next step after continuous delivery. Some organizations combine the automatic deployment process and the Quality Assurance phase (Continuous Testing) but from above comprehensive we are in no suitable condition to combine the two most important phases of development. Both should be catered separately though are combined in Agile methodology but have their own significance.For bigger software we are on constant update in its functionality and it is required to test it upon every release. Thus for such continuous development and deployment of the new features we have to execute the tests to keep the integrity of it.
For every release we have to create the test cases and carry away their execution. The rapid integration and development, being part of agile methodology also have roots connecting to continuous testing. The purpose is simply to verify the new releases and their effects on the preexisting software.
For the purpose of testing we can either execute all the test cases manually or using scripts, the test suit will be compromised of the existing test cases along with the newly created test cases. For each delivery the test suit will be executed. Taking in count for the quick deliverance of the system we will have to keep testing the complete system, thus giving it concept of Continuous testing.
In agile methodology the deliverance is rapid, before making the release go live we have to check it from the testing environment then the UAT link and at the end from live environment. To verify it is according to the

Key Point:

  • Business requirement we have to execute all the test suits.
  • Continuous Testing comprises of following phases
  • Continuous creation of test cases.
  • Continuous improvement in existing test cases repository.
  • Continuous creation of suitable test suits.
  • Continuous execution of test cases.
  • Continuous improvement in the test cases.