CSC/ECE 517 Fall 2016/E1701. Accelerate RSpec testing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
= Problem Statement = | == Problem Statement == | ||
Expertiza tests are really slow. If you check the TravisCI, it needs more than 9 min to run all tests. | Expertiza tests are really slow. If you check the TravisCI, it needs more than 9 min to run all tests. | ||
One reason is that we use fixture to create records in test DB each time running tests. | One reason is that we use fixture to create records in test DB each time running tests. | ||
= Related Work = | == Related Work == | ||
* Classes involved: All RSpec test files in Expertiza. | * Classes involved: All RSpec test files in Expertiza. | ||
* Database involved: Expertiza_test | * Database involved: Expertiza_test | ||
= Task = | == Task == | ||
Formally, you need to: | Formally, you need to: | ||
* Create the records in test DB according to the content in fixtures. | * Create the records in test DB according to the content in fixtures. | ||
Revision as of 21:45, 8 November 2016
Problem Statement
Expertiza tests are really slow. If you check the TravisCI, it needs more than 9 min to run all tests. One reason is that we use fixture to create records in test DB each time running tests.
Related Work
- Classes involved: All RSpec test files in Expertiza.
- Database involved: Expertiza_test
Task
Formally, you need to:
- Create the records in test DB according to the content in fixtures.
- Check each test file and delete certain DB records creation code that insert default records (eg. create(:deadline_type))
- And keep all the test cases passing when using test DB and make sure the time running test cases is shorter than before.
- You should submit the sql file of test DB to expertiza.