1. Test cases should have very good test case coverage.
  2. Test Cases should have good coverage with less no. of steps.
  3. Test Case should be written by applying test case design techniques.
  4. Test Case should be simple to understand.
  5. If test cases given to any new Tester, he/ she should be able to execute the test cases without asking any questions or clarifications.
  6. Test Case should be written in test case template.
  7. Test Case should be consistent, means flow or sequence should be good.
  8. Test Case should consists of both positive and negative scenarios.
  9. Test cases should be able to catch the defects.
  10. Test cases should not be redundant, means no duplicates.
  11. Test Cases should be very easy to convert into Automation scripts.
  1. findElement()
  2. findElements()
  1. close()
  2. get()
  3. getTitle()
  4. getPageSource()
  5. getCurrentUrl()
  6. getWindowHandle()
  7. getWindowHandles()
  8. manage()
  9. navigate()
  10. quit()
  11. switchTo()
  1. getScreenshotAs(args)
  1. executeScript()
  2. executeAsyncScript() — we don't use this for automation
  1. clear()
  2. click()
  3. getAttribute()
  4. getCssValue()
  5. getLocation()
  6. getRect()
  7. getSize()
  8. getTagName()
  9. getText()
  10. isDisplayed()
  11. isEnabled()
  12. isSelected()
  13. sendKeys()
  14. submit()

  1. Primitive type
  2. Non-primitive type

  1. Constructor name should be same as class name.
  2. It will not have return type.
  3. It will not return any value.
  4. It is always non static.
  5. Whenever you create an object, constructor will be invoked.
  1. Non Parameterized Constructor.
  2. Parameterized Constructor.

Sri Priya P Kulkarni

SDET| Blogger! | Automation Nerd! | On a journey of Continuous learning.... !

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store