- July 6, 2017 at 3:49 pm #16650ChrisParticipant@chrishobbs
How much time do you spend familiarising yourself with a piece of software before writing an automated regression pack to cover the basic checks against each build? (Or any other depth of automated testing/checking!)
Is there anything you would always recommend doing before writing your first line of code?July 7, 2017 at 10:17 am #16657TassawerParticipant@tassaweramin
I would recommend that you should first get yourself familiar with the basic functionalities of that software using any of the available resources i.e. User Manual, Interface definition etc.it might be time consuming but its always worth.
Then try writing some basic Manual test for each functionality before gradually shifting them to Automated Ones,July 8, 2017 at 9:57 am #16664ArchanaParticipant@archana
Here is an article on the best practices to follow that may help. You can read it hereJuly 14, 2017 at 8:31 am #16734ChrisParticipant@chrishobbs
Thanks for the reply on this, I definitely agree that the more you know about the software, the better you will be able to target your automation to its needs. I was nervous I didn’t have enough experience in the software before starting a recent automated testing solution, but fortunately things seem to be going well so far!
Here is an article on the best practices to follow that may help. You can read it here
Thanks. This seems like a good set of checkpoints to go through before doing something. It’s in my bookmarks now!July 18, 2017 at 3:12 pm #16772
- You must be logged in to reply to this topic.