asked on Need an automation Test Tool for QA testers (.NET Website)
Need an automation test tool for QA testers
We are considering Selenium...
I need a test tool for non-programmers, because i need the following:
- The first test on a new feature is done by a human
- Before they start the test, the QA tester clicks the Start button.
- The QA tester clicks on various controls and enters various amounts of information
- The tester adds Assertions to the test script, that will be used by the automation to Pass or Fail the test
- When the test is done, the QA testers clicks Done
This is what I want. Does Selenium do this? Any programming required?
Or, are the other tools?
Not sure if it matters, but this is a .NET Framework website...
Thanks
We are considering Selenium...
I need a test tool for non-programmers, because i need the following:
- The first test on a new feature is done by a human
- Before they start the test, the QA tester clicks the Start button.
- The QA tester clicks on various controls and enters various amounts of information
- The tester adds Assertions to the test script, that will be used by the automation to Pass or Fail the test
- When the test is done, the QA testers clicks Done
This is what I want. Does Selenium do this? Any programming required?
Or, are the other tools?
Not sure if it matters, but this is a .NET Framework website...
Thanks
ProgrammingSelenium.NET ProgrammingMicrosoft DevelopmentQuality Assurance
Last Comment
curiouswebster
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
thanks
Right now, in a single Sprint, we have first, second and third rounds of testing.
I am trying to make a business case for building a Selenium script for the first one, then coasting on the second and third rounds of testing.
So, I guess the only question is the comparison (in labor terms) between doing three rounds of testing X 250 tests versus making 250 test scripts.
Then, these functional tests will be added to the regression tests with no further labor.
It sounds like with this kind of potential payback, it's smartest to dive in and start creating tests. If it turns out to be fools gold, it's easy enough to god back to the manual testing route...
Make sense?