CSC/ECE 517 Fall 2016/E1701. Accelerate RSpec testing: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Classes involved: All RSpec test files in Expertiza. What needs to be done: Expertiza tests are really slow. If you check the TravisCI, it needs more than 9 min to run all test...") |
No edit summary |
||
| Line 1: | Line 1: | ||
## E1701. Accelerate RSpec testing ## | |||
Classes involved: All RSpec test files in Expertiza. | Classes involved: All RSpec test files in Expertiza. | ||
What needs to be done: 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. | What needs to be done: 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. | |||
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:39, 8 November 2016
- E1701. Accelerate RSpec testing ##
Classes involved: All RSpec test files in Expertiza. What needs to be done: 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. 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.