You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a saved file has its name changed while the program was not running, then when it starts up again, it is unable to recognize the file. Hence when a user moves to a new computer and a new instance of the code is running, it wont automatically recognize the files.
The text was updated successfully, but these errors were encountered:
This is the intended outcome. When loading the files, the program looks through the notebook.txt If it is unable to find a txt file with the same name in both the archived and unarchived file, it is assumed that the user deleted the file and no longer wants it loaded. However, this behaviour needs to be updated in the UG, hence it is a documentation bug.
Items for the Tester to Verify
❓ Issue type
Team chose [type.DocumentationBug]
Originally [type.FeatureFlaw]
I disagree
Reason for disagreement: This is a feature flaw rather than a documentation bug because nowhere within the UG is it stated that changes to the notebook file would have to be made when importing, leading the user to assume that he can just import the files directly and they will show up in the program. But this is not true and is a flaw on the part of the import functionality.
❓ Issue severity
Team chose [severity.Medium]
Originally [severity.High]
I disagree
Reason for disagreement: This is a high level flaw because without the prior information that the notebook needs to be updated, the user cant import other files.
If a saved file has its name changed while the program was not running, then when it starts up again, it is unable to recognize the file. Hence when a user moves to a new computer and a new instance of the code is running, it wont automatically recognize the files.
The text was updated successfully, but these errors were encountered: