-
Notifications
You must be signed in to change notification settings - Fork 37
ITEP-70721: Add BDD test for label reordering #654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
3cf34a5
to
9988cc6
Compare
3787ef0
to
9e4155d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a BDD test feature for label reordering functionality across different project types. The test verifies that users can reorder labels in projects and that the labels maintain their new order after the operation.
Key changes:
- Implements label reordering step definitions with API integration
- Adds a new feature file to test label reordering across multiple project types
- Introduces helper functions for ordered label retrieval and verification
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
interactive_ai/tests/e2e/features/steps/label_management.py | Adds helper functions and step definitions for label reordering operations and order verification |
interactive_ai/tests/e2e/features/label_reordering.feature | Defines BDD scenarios for testing label reordering across different project types |
Comments suppressed due to low confidence (1)
interactive_ai/tests/e2e/features/steps/label_management.py:222
- [nitpick] The parameter name 'raw_label_names' is inconsistent with the function name which suggests it handles reordering. Consider renaming to 'ordered_label_names' to better reflect its purpose.
def step_when_user_reorders_labels(context: Context, raw_label_names: str):
π Description
Add a BDD test for label reordering
β¨ Type of Change
Select the type of change your PR introduces:
π§ͺ Testing Scenarios
Describe how the changes were tested and how reviewers can test them too:
β Checklist
Before submitting the PR, ensure the following: