Skip to content
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

Duplication of the test folder in the project after it is renamed #1008

Open
dmrock opened this issue May 21, 2024 · 3 comments
Open

Duplication of the test folder in the project after it is renamed #1008

dmrock opened this issue May 21, 2024 · 3 comments
Assignees
Labels
bug something isn't working importer import, check-tests, check-cucumber, sync priority low test tree tests tree, positions, ordering, counters
Milestone

Comments

@dmrock
Copy link

dmrock commented May 21, 2024

Describe the bug
Duplication of the test folder in the project after it is renamed.

To Reproduce
Steps to reproduce the behavior:

  1. Import a new project from Playwright
  2. Rename the main folder
  3. Add new tests
  4. Run the script adding the tags to these tests
  5. Observe the project structure

Expected behavior
All new tests are added to the existing folder and placed in the corresponding sub-folders.

Screenshots
image

Desktop (please complete the following information):

  • OS: MacOS
  • Browser: Chrome
  • Browser Version 124.0.6367.119
  • Application: production

Additional context
Each duplicated folder contains a different set of tests and sub-folders, but they can be duplicated.

@dmrock dmrock added the bug something isn't working label May 21, 2024
@poliarush
Copy link
Collaborator

poliarush commented May 21, 2024

@DavertMik should be have some "move" mode for check-tests that will instruct to move already existed test cases to new locations? what do you think?

or we need some kind of "avoid duplication strategy"

@poliarush poliarush added test tree tests tree, positions, ordering, counters importer import, check-tests, check-cucumber, sync priority low labels May 21, 2024
@DavertMik
Copy link
Contributor

We can think on that
However, as of now we can just prefer the file path when importing
We already do that for files but we also need to do that for folders

@poliarush poliarush modified the milestones: 0.5.36, 0.5.35 May 21, 2024
@poliarush
Copy link
Collaborator

@poliarush poliarush modified the milestones: 0.5.35, 0.5.36 Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working importer import, check-tests, check-cucumber, sync priority low test tree tests tree, positions, ordering, counters
Projects
None yet
Development

No branches or pull requests

3 participants