Skip to content

Instantly share code, notes, and snippets.

@prkhrv
Created October 8, 2017 15:05
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save prkhrv/a360906b2b7bb78caa7f00f22b37b0ee to your computer and use it in GitHub Desktop.
Save prkhrv/a360906b2b7bb78caa7f00f22b37b0ee to your computer and use it in GitHub Desktop.
Selenium:Intro
Selenium is a set of different software tools each with a different approach to supporting test automation.
Most Selenium QA Engineers focus on the one or two tools that most meet the needs of their project,
however learning all the tools will give you many different options for approaching different test automation problems.
The entire suite of tools results in a rich set of testing functions specifically geared to the needs of testing of web
applications of all types. These operations are highly flexible, allowing many options for locating UI elements and comparing
expected test results against actual application behavior. One of Selenium’s key features is the support for executing one’s tests
on multiple browser platforms.
It is not always advantageous to automate test cases. There are times when manual testing may be more appropriate.
For instance, if the application’s user interface will change considerably in the near future, then any automation might need
to be rewritten anyway. Also, sometimes there simply is not enough time to build test automation.
For the short term, manual testing may be more effective. If an application has a very tight deadline,there is currently no
test automation available, and it’s imperative that the testing get done within that time frame, then manual testing is the best
solution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment