Skip to content
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

Full App Tests Tracker #158

Open
97 of 98 tasks
huzaifa-99 opened this issue Nov 29, 2022 · 31 comments · Fixed by #161, #162, #165, #166 or #167
Open
97 of 98 tasks

Full App Tests Tracker #158

huzaifa-99 opened this issue Nov 29, 2022 · 31 comments · Fixed by #161, #162, #165, #166 or #167
Assignees
Labels
documentation Improvements or additions to documentation workflows

Comments

@huzaifa-99
Copy link
Member

huzaifa-99 commented Nov 29, 2022

This issue is to track all web app related tests and the valid test cases that should pass. Any new test case discovered or any update to existing test case should happen on this original comment for better tracking.

Below are some test cases that should work.

IMPORTANT: For each test case, please try at least 2 times

Test Cases

Creation NOTE: When testing anything below with materials, please be sure to test for both cases (1 material and multiple materials)
  • 1- A new non-draft creation without material/s is created successfully
  • 2- Correct data is displayed for non-draft creation without material/s on the creations home page for the creation author
  • 3- Correct data is displayed for non-draft creation without material/s on the creations details page for the creation author
  • 4- Correct data is displayed for non-draft creation without material/s on the creations details page for a public user
  • 5- A new draft creation without material/s is created successfully
  • 6- Correct data is displayed for draft creation without material/s on the creations home page for the creation author
  • 7- Correct data is displayed for draft creation without material/s on the creations details page for the creation author (edit and delete buttons should only be displayed for creation author, preview and share buttons for all users)
  • 8- A user is not allowed to visit details page for a draft creation of another user until that creation is in draft status
  • 9- A creation author is allowed to edit a draft creation without material/s
  • 10- A creation author is allowed to edit a draft creation with material/s
  • 11- A draft creation after publishing has correct data on creation home page
  • 12- A draft creation after publishing has correct data on creation details page
  • 13- A creation author is allowed to delete a non-draft non-ongoing creation successfully
  • 14- A creation author is allowed to delete a draft creation successfully
  • 15- A creation author is not allowed to edit a published creation with or without material/s
  • 16- A new non-draft creation with material/s is created successfully
  • 17- Correct data is displayed for non-draft creation with material/s on the creations home page for the creation author
  • 18- Correct data is displayed for non-draft creation with material/s on the creations details page for the creation author (delete button should only be displayed for creation author, preview and share buttons for all users)
  • 19- Correct data is displayed for non-draft creation with material/s on the creations details page for a public user
  • 20- A new draft creation with material/s is created successfully
  • 21- Correct data is displayed for draft creation with material/s on the creations home page for the creation author
  • 22- Correct data is displayed for draft creation with material/s on the creations details page for the creation author (edit and delete buttons should only be displayed for creation author, preview and share buttons for all users)
  • 23- All external and internal links to other pages work correctly on all creation pages
  • 24- Proper media formats (pdf/image/video/audio/document) are displayed for each creation on all creation pages
    - [x] 25- All Media formats (pdf/image/video/audio/document) work correctly for each creation on all creation pages Redundant of 24
  • 26- Proof of creation dialog should show correct and valid data
  • 27- Avatars should not be displayed on the creation card if there are no external/co-authors
  • 28- Creation Tags should not be duplicated if they are the same lettercase
  • 29- The creation should be correctly validated before sending to api and correct+detailed error response should be shown (this also relates to the user invitation process)
  • 30- A creation should not be deletable if it is in any ongoing process
    - [x] 31- A author should be able to add themselves as a material author in a creation Not Implementing
  • 32- Non-authenticated users should be redirected to a 404 page when they visit /creations/create, creations/${creation_id}/update
  • 33- Recognitions for creation materials should be sent to the correct authors
  • 34- If a creation media cannot be rendered, then show an external link with the link of that media
  • 35- The author search should be case insensitive in creations step 2
  • 36- All creations should be shown by latest first in creations home page
  • 37- Creations search should work correctly on the creations home page
  • 38- Correct creation dates should be shown on all creation pages
Recognition
  • 1- A creation with material should generate a recognition for the author linked with material
  • 2- Correct data should be displayed on the recognitions home page for the recognized author
  • 3- Correct data should be displayed on the recognitions details page for the recognized author
  • 4- Correct data should be displayed on the recognitions home page for author that made recognition
  • 5- Correct data should be displayed on the recognitions details page for author that made recognition
  • 6- Correct data should be displayed on the recognitions details page for a general user
  • 7- A recognition should only be displayed to the recognized author and the author that made recognition on the recognitions home page
  • 8- All users should be able to view the recognition from the recognition details page
  • 9- Proper media formats (pdf/image/video/audio/document) are displayed for each recognition on all recognition pages
  • 10- All internal and external links should work correctly on all recognition page
  • 11- All recognitions should be shown by latest first on the recognition home page
  • 12- The recognized user should be able to respond (accept/decline) to the recognition on the recognition details page
  • 13- Correct creation should be linked to each recognition on the recognition details page
  • 14- A user should be able to share and see proof of a recognition from the recognition details page
  • 15- Correct recognition dates should be shown on all recognition pages
Litigation
  • 1- All litigation links should only be shown to auth users
  • 2- A user should be able to open a new claim (litigation) for a creation of another user (for a creation with no material/s)
  • 3- A user should be able to open a new claim (litigation) for a material belonging to a creation of another user
  • 4- A user should be able to open a new claim (litigation) for a creation of another user if the creation has more than 1 materials
  • 5- A user should not be able to open a litigation for a creation (with no materials) that is owned by themselves
  • 6- A user should not be able to open a litigation for creation material/s that is owned by themselves.
  • 7- A user should not be able to open a new claim (litigation) for an already claimed creation
  • 8- A user should not be able to open a new claim (litigation) for an already claimed material
    - [ ] 9- A user claiming a material/creation should be able to withdraw the litigation (in this case the original author wins)
  • 10-A) - An author should be able to withdraw or disown the creation/material in litigation (in this case the claimer wins)
  • 10-B)- The system should successfully select random reputed users (in range of 3-7) as judges for a litigation
  • 10-C)- A reputed user can be a judge in many litigations
  • 11- A judge should successfully be able to vote in favour of the litigation claimer
  • 12- A judge should successfully be able to vote against the litigation claimer
  • 13- A judge should successfully be able to not vote (or vote undecided/neutral) between the two litigation parties.
  • 14- A judge should only be able to vote once for a litigation (it cannot be changed later)
  • 15- A judge should not be able to vote before the litigation has started
  • 16- A judge should not be able to vote after the litigation has ended.
    - [ ] 17- A claimer should not be able to withdraw their claim before the litigation has started.
    - [ ] 18- A claimer should not be able to withdraw their claim after the litigation has ended.
  • 19- The original author should not be able to withdraw authorship/claim before the litigation has started.
  • 20- The original author should not be able to withdraw authorship/claim after the litigation has ended.
  • 21- Correct winner should be detected by the system based upon the most litigation votes by judges (and on each new vote by a judge)
  • 22- Correct winner should be able to redeem (transfer ownership) of the litigation material/creation for themselves after the litigation has ended
  • 23- Correct data should be displayed for a judge on the litigation home page
  • 24- Correct data should be displayed for a judge on the litigation details page
  • 25- Correct data should be displayed for a claimer on the litigation home page
  • 26- Correct data should be displayed for a claimer on the litigation details page
  • 27- Correct data should be displayed for the original/current author on the litigation home page
  • 28- Correct data should be displayed for the original/current author on the litigation details page
  • 29- All links should work correctly on all litigation pages
  • 30- All dates should be displayed correctly on all litigation pages
  • 31- The litigation status should be updated successfully Failed to update litigation status #109
  • 32- A litigation issuer and assumed author should not be added as a litigation judge
  • 33- A creation (with no materials) in draft status should not be available for litigations
  • 34- A creation material/s in draft status should not be available for litigations
  • 35- A creation (with no materials) that has already been litigated should not be available for litigation again
  • 36- A creation material/s that has/have already been litigated should not be available for litigation again
  • 37 - Correct data should be shown for closed litigations on the home page
  • 38 - Correct data should be shown for closed litigations on the details page
  • 39- An author should be able to start the litigation process (after this the judges of litigations will be able to vote)
  • 40- The ownership of a withdrawn litigation should automatically be transferred to litigation issuer from the assumed author of the creation/material
  • 41- The litigations should be displayed in the 'Waiting authorship recognition' section for a judge before that litigation starts.
  • 42- When a litigation is started it should be displayed in the 'To Judge' section for a judge
  • 43- When a litigation ends it should be displayed in the 'Closed' section for all users.
  • 44- The litigations should be displayed at all times in the 'Waiting authorship recognition' section for a litigation issuer, when a specific litigation is closed only then it should be displayed in the 'Closed' section
  • 45- The litigations should be displayed at all times in the 'Opened against me' section for a litigation assumed author, when a specific litigation is closed only then it should be displayed in the 'Closed' section
  • 46- Invited users should not be added as judges
General
  • 1- Clicking on the profile link (in header) should generate a correct link even on multiple presses
  • 2- Use <Link> from react-router-dom on all pages
@huzaifa-99

This comment was marked as resolved.

@huzaifa-99 huzaifa-99 added documentation Improvements or additions to documentation workflows labels Nov 29, 2022
@huzaifa-99
Copy link
Member Author

huzaifa-99 commented Nov 29, 2022

Discovered Issues from initial tests (will be referenced as DI)

Changes/Nice-to-have things (will be referenced as NTH)

  1. Creations Point 7, 18 and 22 from original comment, I think we should add an edit and a delete button on the creations detail page, and only show these buttons when the creation author visits that page, thoughts @AltiMario? We decided to implement this, created -> Add action buttons on the creation details page #176
  2. Creations Point 31, @AltiMario I remember we had some discussion about allowing this. Currently does it stand as a feature or comes in this ticket? Not implementing for now

@AltiMario AltiMario self-assigned this Nov 29, 2022
@huzaifa-99 huzaifa-99 self-assigned this Nov 29, 2022
@AltiMario

This comment was marked as resolved.

This was linked to pull requests Nov 29, 2022
@AltiMario

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@AltiMario

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@AltiMario

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@AltiMario

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

This was linked to pull requests Dec 3, 2022
@huzaifa-99 huzaifa-99 changed the title WEB - Full App Tests Tracker Full App Tests Tracker Dec 3, 2022
@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@AltiMario

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@AltiMario
Copy link
Sponsor Member

If there are not enough valid users for judgement, the process should be paused (flagging it as pending) until the minimum of users is achieved.
looks complicated but we can continue to keep the process sync as the currently we do.
Every time there is a new ownership claim the system will try to create a new jury for all the pending cases.

@huzaifa-99
Copy link
Member Author

If there are not enough valid users for judgement, the process should be paused (flagging it as pending) until the minimum of users is achieved. looks complicated but we can continue to keep the process sync as the currently we do. Every time there is a new ownership claim the system will try to create a new jury for all the pending cases.

@AltiMario issue created #250. Will be doing this after the other litigation tests as this is kind of an edge case

@huzaifa-99

This comment was marked as outdated.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99

This comment was marked as resolved.

@huzaifa-99
Copy link
Member Author

huzaifa-99 commented Feb 4, 2023

Update

A lot of our litigation workflow were updated in #287 and most of the litigation workflow tests in the OP are invalided

The pending litigation test cases 9, 17 and 18 are also invalidated after #287, so removing them from the tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment