nus-pe-bot
commented
2 years ago Team's Response
From AniList Devs:
Current tab is not a UI detail but rather a feature for the application. Hence mentioning current tab in this use case will not restrict the UI designers in any way.
Furthermore, the use case was created after we have implemented the tab system as a part of evolving design. As such, this use case is meant to be specific to the tab feature.
Our use case complies with the specification given by this module as it does not restrict the UI design.
With that we feel that this is not a bug.
Best Regards!
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Thank you for the response! I disagree based on:
- With regard to:
the use case was created after we have implemented the tab system as a part of evolving design
I believe use cases are created when you embark on a project not during, to specify only external behavior.
- With regard to:
Current tab is not a UI detail but rather a feature for the application.
I think this is wrong since tabs is indeed UI and not a feature. If I may quote your own UG, it's listed under GUI and not Features:
- Trees, accordions, pages, cards, stacks, fans, grids, progressive reveals, filtered reveals are different alternatives to a tab. So this use case has limited UI. Even within the context of anilist, the tabs could've been implemented as a filter command and clearing anime from the "current tab" (UC04 ss'ed in my bug) would've been replaced with an extra parameter to clear.
Therefore, I do believe this use case was written with the fact that UI has tabs in mind. Otherwise, it would be written more along the lines of User requests to clear all watched anime
Best Regards!
This use case assumes an implementation of a tab system in the ui, which goes against the objective of a use case