diff options
| author | Luke "Jared" Bennett <lbennett@gitlab.com> | 2017-05-30 08:40:28 +0000 |
|---|---|---|
| committer | Luke "Jared" Bennett <lbennett@gitlab.com> | 2017-05-30 08:40:28 +0000 |
| commit | 9bb4c08a6e45feb0c6a2c83d7cf0ca5537b61e8a (patch) | |
| tree | a55b1a41a8536af4883f65defdb03ca61214aab7 | |
| parent | 763a3acd033e419f40126cbec6fa7042121686a0 (diff) | |
| download | gitlab-ce-edge-cases-integration-frontend-testing.tar.gz | |
Update testing.md `# Frontend Testing` to include integration spec for edge casesedge-cases-integration-frontend-testing
| -rw-r--r-- | doc/development/fe_guide/testing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/fe_guide/testing.md b/doc/development/fe_guide/testing.md index 0ef9fc61a61..867c83f1e72 100644 --- a/doc/development/fe_guide/testing.md +++ b/doc/development/fe_guide/testing.md @@ -7,7 +7,7 @@ feature tests with Capybara for e2e (end-to-end) integration testing. Unit and feature tests need to be written for all new features. Most of the time, you should use rspec for your feature tests. There are cases where the behaviour you are testing is not worth the time spent running the full application, -for example, if you are testing styling, animation or small actions that don't involve the backend, +for example, if you are testing styling, animation, edge cases or small actions that don't involve the backend, you should write an integration test using Jasmine.  |