A little background of me - I'm a manual tester for almost 2 years within an Agile environment using SCRUM (1-2 weeks sprints).  So I'm wanting to introduce automation testing in my work using Selenium WebDriver (with Java).My question is during when should I test the functionality manually and when should I convert them for automation testing?I have been reading and getting different approach, such as:When a new sprint is starting, convert the user stories to automated scripts from the previous sprint, OR;Convert the user stories within the same sprint.Any advice/s would be very much appreciated. Thank you in advance.
Which stage of Agile (SCRUM) should we start creating automation tests?
testing;agile;scrum;selenium;test automation
Test automation (and all other testing) should be part of the definition of done. This in order to make a potentially shippable product. Can you ship if it wasn't tested?Testing should also be a whole team approach, so test-automation is not the testers responsibility. Start thinking about testing as soon as possible in the process.Test automation is so important in Agile because:Organizational Agility is constrained by Technical AgilityIn other words, when you are slow in making changes to your product, then it doesnt matter how you structure your teams, your organization or what framework you adopt, you will be slow to respond to changes.https://less.works/less/technical-excellence/index.htmlIf you postpone testing until another iteration you will always be lagging behind. Making it harder to change the direction of the product as it is harder to refactor and safe-guard the external behavior of the product. Having any repetitive manual testing is key in slowing you down, automate-it!A lot of testers will tell you that you should not start testing end-to-end until the product interface has stabilized. Don't wait, instead make good use of PageObjects and make sure your tests are maintainable and make it a developer responsibility to create and fix them.