Use graphql boards for project issue boards sidebar specs (EE)
What does this MR do?
Only spec-related changes are included in this MR.
We are working toward rolling out some refactored codes that are sitting behind :graphql_board_lists #248908 (closed) for issue boards and this MR removes the following stub from project issue board sidebar specs (EE), ee/spec/features/boards/sidebar_spec.rb:
- stub_feature_flags(graphql_board_lists: false)Some data-testid attributes have been added to boards components in the process as well.
More information on :graphql_board_lists feature flag.
As mentioned in the above, turning on the feature flag makes project and group issue boards to use newly refactored code internally. There are small differences in appearances and features here and there but the tested subjects of ee/spec/features/boards/sidebar_spec.rb should remain the same with/without the feature flag.
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because the changes don't affect features.
-
-
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 -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
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