I have about 500 test cases to test and I have to test them on all kinds of browsers (IE, Mozilla,Netscape etc) Does anyone know of technique to reduce my work?
Your test cases could be automated so that you can make them all run in one go on different browsers. If you could specify on which technology you are working then a tool could be suggested.
First thing we can do automate the test cases but i'm not sure that's the right selection we can do as below.
-> Categorize all the test cases like what are user interface functional... -> I think most functional cases will works in all browers the failure is 10 out of 100 -> So first i can execute usability issues if the time is there then can go for remaining cases
To execute all 500 in all browsers (IE Mozilla Netscape etc) will definitely take more time.
In our team while doing web application testing we have categorized test cases like Compatibility test cases Integrated Test Cases Functional Test cases etc. so whenever we are are concentrating on different browsers we do execute only Compatibility test cases and give second preferences to remaining test cases. Please correct me if I am wrong
Testing the application with same Test cases with different browsers is some what complicated work. There is no proper technique to reduce the work. One way we can do to this by automation. but not sure the selected tools might be support for all browsers.
Another way is by select and separate those 500 test cases in to little which is common to execute for compatible testing. This also say those selected cases only supports for the compatible testing.
In some browsers even button click could not work as compared with different browsers. To better speech is from the SRS itself clearly mentioned what the vendor needs and what browser they are going to use. The User manual also clearly define that the application supports for following browsers with versions.
As per my understanding we should prioritize our test cases based on the business needs of the functionalities.
For example foe a website we should prioritize our test cases in the following way:
P1: All main page functionalitis like global links main navigation button bar breadcrumbs parent window landing functionalities etc.
P2: Child window functionalities pop ups functionalities secondary pages functionalites and secondary navigation button bars etc.
P3: All error messages default messages system messages and quick menu options.
P4: Pagination options sorting options external links etc.
So in this way according to the time available for testing you can go for testing and also at the same time you can provide testing effort to the management.
PS: All P1 test cases can also be considered as smoke test cases. and all P1 and P2 test cases can be considered as sanity test cases for perticular module.
