Abstract
The main challenge in testing an OOS is that there are large number of test cases which are not feasible to execute all of them within constrained time and budget. This paper proposes some factors which can be used to prioritize the test cases in order to have an effective testing. The considered factors are based on the testing history and structured analysis of the software. These factors may be nature of bug, capability of a test case, execution time, business impact, coverage of code in terms of classes(old and new classes), etc. Every factor has been assigned a positive weight which shows the criticality of the factor and ability to introduce the errors in the software. The prioritized set of test cases thus obtained is helpful to discover maximum bugs as early as possible.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
