diff options
author | Kamil Trzciński <ayufan@ayufan.eu> | 2019-05-22 14:45:46 +0300 |
---|---|---|
committer | Kamil Trzciński <ayufan@ayufan.eu> | 2019-05-22 14:45:46 +0300 |
commit | 4f20c9de6f8e09131d751174243214d9bd3b6419 (patch) | |
tree | b41332bd3773178776ff92738de8cff3f84fc689 /doc/development | |
parent | c4d930e5f54e7da07c80cc028dfc0f5c08719146 (diff) |
Revert "Merge branch 'reorganize-tests-jobs-by-level' into 'master'"
This reverts merge request !27514
Diffstat (limited to 'doc/development')
-rw-r--r-- | doc/development/rake_tasks.md | 13 | ||||
-rw-r--r-- | doc/development/testing_guide/testing_levels.md | 12 |
2 files changed, 9 insertions, 16 deletions
diff --git a/doc/development/rake_tasks.md b/doc/development/rake_tasks.md index f06ffab03c6..27fc3231218 100644 --- a/doc/development/rake_tasks.md +++ b/doc/development/rake_tasks.md @@ -108,13 +108,11 @@ To make sure that indices still fit. You could find great details in: In order to run the test you can use the following commands: -- `bin/rake spec` to run the rspec suite -- `bin/rake spec:unit` to run the only the unit tests -- `bin/rake spec:integration` to run the only the integration tests -- `bin/rake spec:system` to run the only the system tests -- `bin/rake karma` to run the karma test suite +- `rake spec` to run the rspec suite +- `rake karma` to run the karma test suite +- `rake gitlab:test` to run all the tests -Note: `bin/rake spec` takes significant time to pass. +Note: `rake spec` takes significant time to pass. Instead of running full test suite locally you can save a lot of time by running a single test or directory related to your changes. After you submit merge request CI will run full test suite for you. Green CI status in the merge request means @@ -123,9 +121,6 @@ full test suite is passed. Note: You can't run `rspec .` since this will try to run all the `_spec.rb` files it can find, also the ones in `/tmp` -Note: You can pass RSpec command line options to the `spec:unit`, -`spec:integration`, and `spec:system` tasks, e.g. `bin/rake "spec:unit[--tag ~geo --dry-run]"`. - To run a single test file you can use: - `bin/rspec spec/controllers/commit_controller_spec.rb` for a rspec test diff --git a/doc/development/testing_guide/testing_levels.md b/doc/development/testing_guide/testing_levels.md index b5155b6b7fa..1fa6e38ea5a 100644 --- a/doc/development/testing_guide/testing_levels.md +++ b/doc/development/testing_guide/testing_levels.md @@ -4,14 +4,12 @@ _This diagram demonstrates the relative priority of each test type we use. `e2e` stands for end-to-end._ -As of 2019-05-01, we have the following distribution of tests per level: +As of 2019-04-16, we have the following distribution of tests per level: -| Test level | Community Edition | Enterprise Edition | Community + Enterprise Edition | -| --------- | ---------- | -------------- | ----- | -| Black-box tests at the system level (aka end-to-end or QA tests) | 68 (0.14%) | 31 (0.2%) | 99 (0.17%) | -| White-box tests at the system level (aka system or feature tests) | 5,471 (11.9%) | 969 (7.4%) | 6440 (10.9%) | -| Integration tests | 8,333 (18.2%) | 2,244 (17.2%) | 10,577 (17.9%) | -| Unit tests | 32,031 (69.7%) | 9,778 (75.1%) | 41,809 (71%) | +- 67 black-box tests at the system level (aka end-to-end or QA tests) in CE, 98 in EE. This represents 0.3% of all the CE tests (0.3% in EE). +- 5,457 white-box tests at the system level (aka system or feature tests) in CE, 6,585 in EE. This represents 24.6% of all the CE tests (20.3% in EE). +- 8,298 integration tests in CE, 10,633 in EE: 0.3% of all the CE tests (0.3% in EE). This represents 37.2% of all the CE tests (32.8% in EE). +- 8,403 unit tests in CE, 15,090 in EE: 0.3% of all the CE tests (0.3% in EE). This represents 37.8% of all the CE tests (46.6% in EE). ## Unit tests |