-3

The application has to be automated. What test cases I will consider to automate .

  • 2
    I downvoted this because it is too broad. – user246 Jun 26 '15 at 15:10
  • 1
    If you give more detail the answers your receive will be more precise. And probably much more useful. – Bookeater Jun 26 '15 at 18:41
  • Not a hint of any of your own effort. Books were written on the subject. – Peter M. - stands for Monica Jun 26 '15 at 20:44
1

A generic answer here is:

  1. Essential stuff like login. It's a start.
  2. Easy to automate functions to acquire some coverage, fast.
  3. Bugs as you encounter then, this is good practice and already receiving attention anyway.
  4. Fragile functionality as determined by your developers.

This list goes on, of course. In the end 100% coverage is the goal. Which never will be reached. But that is another story.

1

When trying to figure out what to automate I like the questions (and advice) from this Elemental Selenium Tip. It basically says

A great way to increase your chances of automated web testing success is to map out a testing strategy. And the best way to do it is to answer these four questions:

  1. How does your business make money?
  2. How do your users use your application?
  3. What browsers are your users using?
  4. What things have broken in the application before?

Then you map out a strategy based on these ideas. I like to throw my strategy into a Mindmap so I can share it with the rest of the team.

Sure you can automate easy things but ideally you'd be able to start with the easy as you work towards the important things.

Not the answer you're looking for? Browse other questions tagged or ask your own question.