Page Comparison

List of task by priority:

1. Add new teststests (no need to commit to branch)
   1. contract tests, manage and add tickets for missing tests – 

      Jira Legacy
      server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1012

       (no need to commit to branch)
   2. performance tests - 

      Jira Legacy
      server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3623

       (no need to commit to branch)
   3. functional tests - 

      Jira Legacy
      server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-4569

       (no need to commit to branch)
2. Groom the TechDebt backlog by first prioritizing in the issue list, and then by ranking them on the board (more details on Dev Group)
3. Walk through code to find tech debts, create tickets for them, add label TechDebt.
   1. add, review and/or improve unit/integration tests. Like rework them to use test data builder pattern, fix and reenable disabled tests, remove or improve tests that don't make any sense, etc.
4. Quick win tickets – https://openlmis.atlassian.net/issues/?filter=20549 (take by priority - from top to bottom, commit to branch if necessary)
5. Fixing tech debt  – https://openlmis.atlassian.net/issues/?filter=20544 (take by priority - from top to bottom, commit to branch if necessary)
6. Refining backlog bugs
7. Overview of test cases
8. Familiarizing with Stock Management documentation