Developed an automated test prioritization tool that can be used with any java project to prioritize unit test execution in order to discover bugs faster. Technologies used: Java, Maven, JUnit, Java Agent, ASM Bytecode Manipulation Framework Without manipulating or even knowing the structure of the source code or unit tests, this tool can be deployed on any project to create a new - prioritized test suite. Say you have a 100,000 unit tests in your project and it takes a few hours for all the unit tests to run. Now, if there was a strategy that could run these unit tests in a specific order of priority, so that you could discover bugs faster wouldn't it be very helpful and save you tremendous amount of time in discovering bugs? The answer is yes. The strategy we have implemented to achieve this is Automated Test Prioritization using statement coverage information of unit tests. Statement Coverage: Number of (unique) source code lines that are covered by a unit test. The Test Prioritization is based on two strategies: Total and Additional strategies. Total strategy - The unit tests with highest statement coverage are prioritized first. Additional strategy - The unit tests which cover maximum number of 'yet uncovered' source code statements, by previous unit tests, are prioritized first. The experimental data shows that these strategies are able to detect bugs faster rather than randomly executing the test suite. Logically, a unit test covering more lines will have a higher priority of detecting bugs than a test covering few lines.