Forum Discussion
Hi Darshana,
Copied from http://www.softwaretestinghelp.com/10-tips-you-should-read-before-automating-your-testing-work/ :manwink:
Automate your testing work when your GUI is almost frozen but you have lot of frequently functional changes.
Writting automation test when the UI is not stable is not a good idea. You will be totally unaware of the control properties which you can use in automation script.
We have faced a similar situtation . We use keep lag of 1 sprint to complete our automation work.
Ex :
Sprint 1 :
Dev creates new UI part & new functionality
Tester prepares test scenarios to be automated
Sprint 2:
Dev works on new task
Tester automates what has been developed my dev in previous sprint.
I hope this has been of some help.
Thanks Vajinderladdad,
I would like to know that ,how actually the automation has applied on agile projects?
Is the same regreassion,load and performace scripts are used?
or actually scripts for unit test(developed by programmer) is used for automation of the functional testing in testing?
whol develop the automation scripts for agile projects?devloper or tester?
Thanks for your guidance.
Regards
Darshana
- vajindarladdad10 years agoFrequent Contributor
Hi Darshana,
We were creating the regression test and adding it to our regression suit
In addition to that we were creating API tests for the same which does not require any UI.
Coming back to your questions:
Q) How actually the automation has applied on agile projects?
A) First , you need to understand what new is being developed in the currect sprint , then you need to analyse which test would suit best to check the functionality (API , UI based test etc. )& then develop the test.
I think creating API Test would suit more for your requirement.
Q) Is the same regreassion,load and performace scripts are used?
A) Yes , You can use the same suit but minimal modification may be required.
- Marsha_R10 years agoModerator
We use agile and we do our automation in the same sprint as the developers work. The developers give us the framework as soon as they can so we can do name mapping while they are finishing. It may need to be changed a little for the final product, but usually not much. We plan the tests while the developers are working and then we do our coding in TestComplete when we get the final product.
We tried delaying it one sprint when we first started and for us it seemed to be too much like waterfall. The developers have moved on to something else and have to change focus back and forth if we have questions while testing. By including the automated testing in our definition of Done, we are able to stick together.
- mgroen29 years agoSuper Contributor
Marsha_R, Darshana, blacy, vajindarladdad
I am facing similar situation. The company I am working for right now is using Agile and CI/CD (Continious Integration / Continious Development), and feedback on the tests is important and needs to be done quickly.
So, there is no time for extensive scripting, because every day new software is delivered so all maintenance on the framework needs to be done in max. 8 hours.
Also, we need to automate as much as possible (to test as much possible in the available time), and maintenance on the automated tests needs to be every efficient en fast.
I like TC as test automation tool, but I think it has its shortcomings in Agile/ CI / CD environments.
That is why I want TC to be more intelligent on signalling changes in the UI of the AUT (Application under test).
There is a discussion on this thread
Also, I have 2 feature requests which I think would greatly improve TC in handling Agile / CI/CD software approaches.
These can be found here and here
Hope you share your feedback
Related Content
- 12 years ago
- 14 years ago
- 8 years ago
Recent Discussions
- 18 hours ago
- 19 hours ago
- 5 days ago