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.

Sign up for GitHub

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

Jump to bottom

--no-empty option seems to be ignored on backend #135

Closed
tikolakin opened this issue Sep 29, 2023 · 4 comments
Closed

--no-empty option seems to be ignored on backend #135

tikolakin opened this issue Sep 29, 2023 · 4 comments
Assignees
@olexandr13
Labels
bug Something isn't working priority medium
Milestone
0.5.34

Comments

@tikolakin
Copy link

tikolakin commented Sep 29, 2023 •
edited
Loading

Describe the bug
There seems to be a no way to get rid of empty test suites

To Reproduce
I have tried to import test with both options

Screenshot 2023-09-29 at 18 10 46 Screenshot 2023-09-29 at 18 09 18

After import - empty suite remains available
image

Expected behavior
When noempty is sent as true - Testomatio removes empty suites
@tikolakin tikolakin added the bug Something isn't working label Sep 29, 2023
@tikolakin tikolakin changed the title --no-empty option seems to be ignored --no-empty option seems to be ignored on backend Sep 29, 2023
@tikolakin tikolakin mentioned this issue Feb 4, 2024
Closed
@poliarush poliarush added this to the 0.5.33 milestone Feb 6, 2024
@TetianaKhomenko
Copy link

Hi @tikolakin! The issue was fixed. The fix will be published in the next release.

@TetianaKhomenko
Copy link

Hi @tikolakin the fix is live now. Please check it and reply if it works for you.

@tikolakin
Copy link
Author

It doesn't work, after importing with --no-empty. Tested with https://github.com/testomatio/check-tests/releases/tag/0.8.24
Empty folders/suites are created in testomatio
Also, recent changes seem to introduce a regression to the folder structure, prefixing it with the source folder. It wasn't like it before.

@poliarush poliarush reopened this May 21, 2024
@poliarush poliarush modified the milestones: 0.5.33, 0.5.34 May 21, 2024
@Fro0z1k Fro0z1k assigned DavertMik and unassigned Fro0z1k May 22, 2024
@TetianaKhomenko
Copy link

Hi @tikolakin! The issue should be fixed now. Can we ask you to check it on new imports?

@olexandr13 olexandr13 assigned olexandr13 and unassigned DavertMik Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olexandr13 olexandr13

Labels
bug Something isn't working priority medium
Projects
None yet
Milestone
0.5.34
Development

No branches or pull requests
6 participants
@DavertMik @poliarush @tikolakin @Fro0z1k @olexandr13 @TetianaKhomenko