Improve spec coverage for tasks on boards behind FF
What does this MR do and why?
This code change improves test coverage for a board issues listing feature by making the tests more thorough and realistic. The main changes include:
-
Making projects public by default - Tests now use public projects instead of private ones, which better reflects real-world usage where most projects are publicly accessible.
-
Adding task-type issues to tests - Some test issues are now marked as "tasks" (a specific type of work item) to ensure the system properly handles different issue types.
-
Testing anonymous user access - The tests now verify what anonymous (not logged in) users can see when viewing project boards. For public projects, they should see most issues, but for private projects, they should see nothing.
-
More specific test expectations - Instead of just checking that results exist, the tests now verify the exact issues and issue types that should be returned in different scenarios.
-
Adding private project test cases - New tests ensure that when a project is made private, anonymous users cannot access any of its issues.
These changes make the tests more comprehensive by covering different user permissions, project visibility levels, and issue types - ensuring the board listing feature works correctly for all users in various situations.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.