a very basic question - automation testing with CI
Posted: Mon Jan 26, 2015 12:50 pm
Hi,
As per this blog http://www.ranorex.com/blog/integrate-r ... on-process, the ranorex test gets executed as part of build process as soon as a developer commits a change. This helps provide rapid feedback and is in-line with agile process etc. etc...
I am confused how this is possible in, for example a web based application.
Shouldn't the ranorex tests run after deployment of AUT in a test environment.
As per my understanding the steps should be as follows:
1. developer commits change in SVN.
2. Bamboo starts build.
3. if compile/unit test fails, developer is notified. She fixes tests. goto step 1.
4. if compile/unit test succeed then an artifact is created (such as jar or war) and is pushed to Nexus.
5. Team lead/manager coordinates with dev/test teams and decides if it is the right time to do a release in testing environment. If yes, then run deployment script and performs application deployment.
6. If deployment succeeds then as a last step of deployment Ranorex test will kick-in and perform testing.
7. Testers monitor success/failure of Ranorex test results and raise bugs(regression) as per outcome of test execution.
8. developers fix bugs and repeat step 1.
In above flow there is no rapid feedback as mentioned in blog entry. The releases are not as frequent as commits by developers and the feedback will come only when ranorex test fails after deployment of application in a testing environment.
Am I missing something?
Regards,
Ravi
As per this blog http://www.ranorex.com/blog/integrate-r ... on-process, the ranorex test gets executed as part of build process as soon as a developer commits a change. This helps provide rapid feedback and is in-line with agile process etc. etc...
I am confused how this is possible in, for example a web based application.
Shouldn't the ranorex tests run after deployment of AUT in a test environment.
As per my understanding the steps should be as follows:
1. developer commits change in SVN.
2. Bamboo starts build.
3. if compile/unit test fails, developer is notified. She fixes tests. goto step 1.
4. if compile/unit test succeed then an artifact is created (such as jar or war) and is pushed to Nexus.
5. Team lead/manager coordinates with dev/test teams and decides if it is the right time to do a release in testing environment. If yes, then run deployment script and performs application deployment.
6. If deployment succeeds then as a last step of deployment Ranorex test will kick-in and perform testing.
7. Testers monitor success/failure of Ranorex test results and raise bugs(regression) as per outcome of test execution.
8. developers fix bugs and repeat step 1.
In above flow there is no rapid feedback as mentioned in blog entry. The releases are not as frequent as commits by developers and the feedback will come only when ranorex test fails after deployment of application in a testing environment.
Am I missing something?
Regards,
Ravi