Skip to content

Conversation

@josenavas
Copy link
Contributor

Built on top of: #1647 so review/merge that one first.

Here I split the tests of processing job, software and artifact between read/write and read/only, as well as grouping tests that are testing the same thing. This reduces the amount of times the database needs to be reset. Times:

  • Artifact: From 1m59.500s to 0m32.497s
  • Processing job: From 1m34.795s to 0m30.331s
  • Software: From 1m34.751s to 0m7.590s

@josenavas
Copy link
Contributor Author

That's interesting, reducing the running time of the tests in my machine by ~4 min is equivalent to ~30 min in Travis? Wow - I saw that there are a couple of failures, I'm gonna fix them here.

@antgonza
Copy link
Member

I can confirm this behavior from my other improving-tests tests. However, I can't explain why.

… warning and the stochacity of the order in which the tests are executed
… into artifact-study-pages-tests-reduce-qiita-db
@josenavas
Copy link
Contributor Author

This is ready for review. The main changes here are splitting the tests between read-only and read-write. I've also fixed the last 3 tests that were failing, which where mainly due to the usage of sets which makes the output order undefined.

@antgonza
Copy link
Member

👍

1 similar comment
@ElDeveloper
Copy link
Contributor

👍

ElDeveloper added a commit that referenced this pull request Feb 28, 2016
…duce-qiita-db

Reduce tests running time for qiita_db
@ElDeveloper ElDeveloper merged commit 946970f into qiita-spots:artifact-study-pages Feb 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants