Can someone tell how to run a regression test with E-Test?
What are the steps/
Do i need Data Bank ( i.e. for Login scripts)
For instance, there's a baseline agains which we run a regression test.
If some new feaures were added to the application, during playback it should give me an error, but it's not an actual 'bug'.
So to handle this king of things?
Do i need to modify scripts manually?
Depends on philosophy and methodology. We don't regress against changed applications/systems. New functionality is tested at system and integration level. Regression for us is the final end to end test of a "finished" product. So our errors ARE bugs. To do our regression we record/script out scripts and run them iteratively followed by 3 levels of performance tests, analysis, load and stress using the same scripts as for our automated regression test
Information Engineering and Software Quality Assurance Specialist
Your questions are very general and (as the previous response indicates) are more related to the methodology you choose than to e-Tester.
1. How do you run a regression test?
The simplest way is to use the record feature of e-Tester, save the recorded script, then play it back.
When you play it back, any differences it finds from the recorded pages will be reported (depending on how you've set your default tests).
You can also record a series of scripts, then use e-Manager to put them together as a "job" and run them.
2. Do you need a DataBank?
The DataBank is used to fill in fields with variables. You can use the DataBank to loop through a script and have it enter a different value in the same field everytime it loops through. For example, you might have username and password fields that you want to test. Using the DataBank, you could create hundreds of username/password recordsets and have e-Tester try each of them.
Data in the DataBank can be external (usually kept in a .CSV file) or internal (a calculated value).
So you don't "need" to use a DataBank, but it's available if you have a need.
3. If some features were added...?
This gets problematic. A recorded script references objects on your page by creating an index. It then tests and acts on these indexed objects according to how you've set your test up.
If you make a changes to your page, it is very likely that e-Tester will "re-index" some of the objects (like input fields or buttons). If you have recorded any actions on objects that get re-indexed, you will get a "Navigation" error. You can go in and edit your recorded script to correct this or re-record your script. You can also control what happens when you get this error (to some degree).
Yes you can get errors that are not really bugs.
I would politely suggest that you experiment with e-Tester. Play with all of its features. Explore the different default testing it does, try customized tests and the use of VBA.
If you use a combination of recording and programming, you can build some very robust scripts that require low maintenance and will serve your regression requirements.