Issues found during testing v1.6

[osrmt]

Issues found during testing v1.6

[rpandhurkar]

I have implemented most of the bugs which are reproducible.
Please find attached sheet for more details
Bug Fixing Status - 130419.xlsx

Here are the final statistics :
Total Bugs : 19
Implemented : 12
Duplicate : 1
Not Reproducible : 1
Working As Per Design : 3
Need Enhancement : 1 --> Opened issue 19 to track this issue.
Moved to Next Sprint : 1 --> Opened issue 18 to track this issue.

[kumarkishore1001]

Hi,
I have re tested all the issues.
Please find the attachment here:
Total Bugs : 18
Failed: 9
Pass: 3
Moved: 2
Suggestion(For better functionality): 4

PFA

Kishore's Comment Bug Fixing Status.xlsx

Thanks,
Kishore

[rpandhurkar]

Hi Kishore,
I tried to reverify it again post checking your retesting result but am able to recreate only one issue which I had closed earlier as Return->Working as per design all other issues are working for me kindly check following detailed analysis with screenshots, I have done re-verification on windows, I am in process to re-verify it on MAC as well for which I will add additional comments.

Screenshots of Bug 1,2 and 19
It is working fine for me please find attached screenshots

Bug 3:
You had specified for menu in recreation steps so that have been fixed for toolbar please open separate issue, menu is fixed kindly check screenshot

Bug 4:- As verified by you its working fine

Bug 5 & Bug 6:
This issue was opened for just for correcting error message, since that was the exception we have corrected the ui, so that buttons would be disabled itself as to save steps for the test case first you need to save the test and then update the steps. ( this is applicable for all new artifacts whether that is Test case or Requirement), Kindly verify that you should not get any error on the screen)

Bug 7 : As verified by you its working fine

Bug 8 :
Export Reference not working-- Working for me, kindly check screenshot

Exported reference files and screenshot

system_details.log
system.log

Bug 9: As verified by you its working fine

Bug 10: Enhancement, We have moved it to 1.8

Bug 11:
Working for me
As I mentioned above there is a limitation with OSRMT that for most of the additional details to be added you need to save artifact first and then perform additional task, this is one of such action, earlier error message was not getting displayed which I have enabled.

Bug 12:
Working for me
Please check attached screenshots

Bug 13 & Bug 14
Working for me
please check attached screenshots

Bug 15:
I had closed this earlier marking working as expected as by clicking sync button it was working for me but now I am able to recreate the issue.

Bug 16 & Bug 18
These were opened as questions so answers were provided for the questions asked, No changes were expected as part these bugs opened so only investigation details were provided.

Bug 17: This is already moved to 1.8

So to conclude I am able to recreate only one issue which I had closed earlier as Return->Working as per design

Kindly let me know whether we should have joint session to verify issues you are facing.

[rpandhurkar]

Ritesh.Comments.Bug.Fixing.Status.xlsx

[kumarkishore1001]

Hi Ritesh,

All the issues are tested on Mac OS Mojave 10.14.1
Following are my comments against each Bug:

Bug 1
No error message is displayed.

Bug 3
Menu was just one of the example. Behaviour should be same throughout the application. For me it comes under 1 ticket but for your convenience I will create another ticket.

Bug 5 and 6
Technically the solution to these bugs created more critical bug where user is not supposed to save the cases in the first attempt. It is a bad user experience and we can't force user to just save the title while creating the test cases and come back for editing to save the step.

Bug 8
I got the success message as well but not sure where it get saved. User should know where it should be saved.

Bug 11
I am still not convinced that user will not be able to do certain things while creating something new. It is still an issue with me, though I will raise it to relevant person to get better understanding of this.

Bug 13 and 14
Why I am able to select any file in export? I have tried with jpeg and it accepted it. And then my jpeg file got corrupted.

Bug 15
As tested by you too it is not working.

Bug 16 & 18
I will still consider it as a bug as this is not what a user should expect from the application. Though you are correct that it should be discussed.

[kumarkishore1001]

Closed by mistake.

[rpandhurkar]

Hi Kishore,

Please find my responses below.
Bug 1) I will verify this on MAC since on Windows its working fine for me, If I would not able to its specific to your version MAC then I would be needing to debug on your machine directly.

Bug 3) I agree with you but in defects generally only whatever mentioned has been addressed and while making changes if something additional is identified then it will be treated as new defect.
Thanks for opening new defect.

Bug 5 and 6
Since this is how OSRMT has been developed but if we want to change the behavior we need implement the functionality so that is something goes under enhancement/change request.

Bug 8
Please check under desktop folder/ at the same location where you have executed run command.

Bug 11
I agree with you, but since this is how it has been developed so I just corrected what was wrong so that in the flow, but if we want to change the flow/functionality then that would go under enhancement/change request.

Bug 13 & 14
You need to provide file name to export do not specify any extension or do not select any existing file name as shown in figure test3 is the name for export file is provided.

Bug 16 & 18
Since what was asked in the bug has been provided so I cant consider keep this open now, If you need any further changes on the basis of analysis provided as part of questions asked then please open separate issues.

[rpandhurkar]

Hi Kishore, I am able to recreate bug1 on MAC

[rpandhurkar]

For Bug 8, please ignore above comment and refer following.

When you get successful message please check Schema folder is created under root folder where run.sh is available, under schema folder you can see all files created.
Kindly refer below screenshot

[rpandhurkar]

Hi Kishore,

You can refer following attached document for results verification, I have added additional comments with screenshots for some of the scenarios.

Bug Resolved_1-18.docx