-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Manager cannot handle corrupted scenario files. #240
Comments
…3#240 + some minor corrections
I slightly disagree with the expected behavior, what you've shown here is what I would expect as the behavior for this scenario file, as long as the GUI doesn't crash and remains usable this working as it should.
Because the the data for "Example Test Case" is row 7 but the scenario says only 3 rows should be there, row 7 should not be loaded, If a user manually modifies a scenario to remove rows, they also should update the row number of the row data to reflect the row position they want it to have
|
Hmm i think you're right, the Manager should work like this and if the user decides to modify the scenario file, he must be careful with the structure. I also found one more thing: If i load this scenario file, the Manager will add extra row.
|
Ah it should also work like this the first index is not zero :) |
No it's not zero, because if the first row in the GUI had an index of 0 it would look weird, and I wanted the index in the file to match what it shows in the GUI. |
Bug fix for Issue #240 - Manager cannot handle corrupted scenario files.
Merged into release branch v1.3.1 and all test passed |
Describe the bug
When you open a corrupted scenario file in Manager it is unable to repair the scenario file and get information's form it.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Screenshots
When you try to open it:
After restarting program, the Manager will reopen with the scenario file:
Additional context
test.rfs file:
The text was updated successfully, but these errors were encountered: