Some days back i was analyzing different tools which would help me to automate my tests.Keeping in mind the features which different tools provide and the constraints we had,it was decided to extend some existing free source automation tool to serve our purpose.So i prepared a list of features which i would expect from a test framework.....
The points are mentioned below for your reference.If i have missed some point then please feel free to add to this list:)
1.Should be able to handle controls like lookups,dialog handlers,alerts etc
2.Should be browser(IE6,IE7,mozilla etc) compatible
3.Flexible enough to bring control to parent or child windows
4.Should keep track of results
5.All the control names should be stored in xml or config file or excel file whichever is best suited
6.Should accept input from xls or some other source externally(No need to go ahead and put input parameters in code)
7.Should have generic method to identify controls
8.Should not affect the performance of the application to great extent
9.Should be able to handle exception rather than failing abruptly
10.Should be able to identify controls and look for it depending upon its type e.g.,Identifies a picklist control and searches for control only of picklist type
The above list includes a basic set of features and is common both for website or any specific domain e.g., MSCRM....
some other points:
ReplyDelete1. Should support tagging the various test cases.
2. Should let us run only a set of the tagged test cases, eg: run all the P0 tests.
3. If coded on our own then the code should be written in such a way so that adding a new test case requires minimum (ideally zero) amount of new code.
Nice...will help me get through my exam
ReplyDelete