Trav1sT / pe

0 stars 0 forks source link

Entries are not listed after check command is called #7

Open Trav1sT opened 4 years ago

Trav1sT commented 4 years ago

After I Key in 'check 2020-11-13' I expect to find a list of journal entries as shown in the UG. However, I got this instead. Update: I have added in multiple journal entries made on 2020-11-13, one of them has a super long name as shown below.

image.png

nus-se-bot commented 3 years ago

Team's Response

The GUI does not actually crash, you can still switch to viewing other entries using the viewj command and the product would still be usable after.

This should not be a bug that happens very much, as titles are not expected to be too long. Users can also resize the window to view the full title, provided that the length is still reasonable.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Low] Originally [severity.High]

Reason for disagreement: I mark this as High because the whole function of check (unlike viewj <name of a journal with long title>) is to "Finds a list of journal entries" as given in the UG. It is to let the user have a quick access to whatever they had written for that day. Yes, I can still view other journals by using viewj command. However, this is a unintuitive. I do not know how many journals and what journals I have on that specific day (it could be very long ago). So I have to execute numerous viewj <some random valid number of an entry> and then find out what the first entry of the day I am interested in then execute numerous viewj <some random valid number of an entry> till I have the last entry of the day I am interested in? Or I could listj then scroll through the long list.

Let's say I wrote 3 journal entries. But the first one has a long title. So, 1 month later, I run check <date> then all I am seeing is the screenshot above. Maybe I had only written 1 entry on that day 1 month ago? I will cant know.

There are numerous fixes such as wrapping of title, truncating it, make the panel horizontal scrollable. All of which won't require much effort to implement.

It is not tat uncommon especially during testing I have a very limited screen space(to view UG, DG, run the application, view testing rubrics). So I reduce the size of the app. So it takes just a dozen words to overflow.

Perhaps it could be severity medium since the product technically did not crash and we only had like 6 weeks to do this. However, it did affect the normal operation (which is to see a list). Hence, it should not be Low.