WIP: Resolve "Test cases and test suites"
WIP
and I don't know what kind of shape it's in due to originally being created on the CE branch. I tried to pick it up during hackathon, ran into issues, and want to get back to it to move it forward due to that it'd be useful to me. I'm just posting MR here now so I can keep easier track of it because I've lost it more than once.
If you're reading this and you can assign, assign to me for now until I have a better idea. When it starts to take shape, I'll be sure to find and ping someone who might be able to review.
What does this MR do?
Starts picking up where gitlab-foss#56215 (moved) and gitlab-foss!26802 (closed) left off.
The goal is to get the test cases & suites functionality implemented at the minimum viable level, based on the original issue mockups and on the MVC description outlined in &617
-
Can create a test suite for a group -
A test suite can have a Markdown-formatted description -
Can create multiple test cases inside a test suite -
A test case can have a Markdown-formatted description -
A test case can have a field indicating whether it is manual or automated -
A test session can be created to contain test results for a test suite. The default result is "Pending", meaning it has yet to be run -
A test result, "Passed", "Failed", maybe "Not Run" can be associated with the case for that session -
An API call can be made from an automated test that starts a test session -
An API call can be made from an automated test that sets a test result for that session
Why? To replace Google Docs/Excel, repurposed GitLab issue boards, or separate test organization tools.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #26097