Combine frontend and backend testing level documentation

We should combine

• https://docs.gitlab.com/ce/development/testing_guide/testing_levels.html
• https://docs.gitlab.com/ce/development/testing_guide/frontend_testing.html#overview-of-frontend-testing-levels

into one guide—optionally making the detailed descriptions of each level a sub page.

added Quality development guidelines documentation test labels

optionally making the detailed descriptions of each level a sub page.

@marcia Does this make sense to you?

For example we would then have https://docs.gitlab.com/ce/development/testing_guide/testing_levels/unit_tests.html which is linked to from the overview at https://docs.gitlab.com/ce/development/testing_guide/testing_levels.html.

@winh sorry, I missed your ping.

Can you give a little bit more context? Like, why would you like to join them/what's the advantage of doing so? Are both guides used by the same teams (FE and BE)?

Can you give a little bit more context?

@marcia Sure—sorry for leaving that out earlier!

Some testing levels are relevant for backend and frontend (namely white-box tests in spec/features/ and black-box tests in qa/qa/) because they test the application at a high abstraction level. Having them documented on the Testing levels page while frontend tests are a separate page can lead to the impression that they are not relevant for the frontend.

Additionally some best practices and general principles apply to backend and frontend in a similar way (mostly in the unit testing area). Having them at the same place leads to less repetition / duplication.

Especially for community contributors and new team members it may also help to have an overview of all test levels there are (rather than having it split across two pages).

Moving the test levels to their own pages gives us the opportunity to add more detail and examples without making the currently existing testing levels page too overwhelming.

Does this explanation make it more clear?

added devopsverify docs-only labels

@rdickenson this is actually gitlab-ce4107632, not a devops stage (gitlab-ce3103453)

removed devopsverify label

Got it, thanks @winh! It does make sense. Please feel free to merge both into one.

@donaldcook I'd like to give this a try in %12.2. Please let me know if you think it doesn't fit.

changed milestone to %12.2

added Plan [DEPRECATED] label

changed weight to 1

added [deprecated] Accepting merge requests label

added frontend label

My first questions are,

1. I think new_fe_guide phrasal is not elegant for URL.
2. At last should we have single page or URL for all two page after combination operation?
3. Is it appropriate to add folders or directories to

https://docs.gitlab.com/ce/development/new_fe_guide/development/testing

like,

• Unit tests
• Integration Tests
• etc.

and they become

https://docs.gitlab.com/ce/development/new_fe_guide/development/testing/unit_tests.html

https://docs.gitlab.com/ce/development/new_fe_guide/development/testing/integration_tests.html

etc.

According to my first MR, i think asking questions with possible simple answers is a good way to start to contribute. I have a merged MR which i achieved with simple directives.

@temizerm we're planning on removing the new_fe_guide directory entirely (moving to fe_guide).

The test docs are all being moved to https://docs.gitlab.com/ce/development/testing_guide/frontend_testing.html

That is currently all one page. I am not sure if they are plans to split it further

here is the corresponding issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/56376

and here is the corresponding merge request: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31852

added devopsplan label

changed milestone to %12.3