Page Comparison

The code freeze period is dedicated to regression and performance testing, as well as fixing critical and blocker bugs. However, usually not everyone in the team is involved in it (eg. because there's only last test case remaining or there's only last bug being worked on).

...

•  Update links in https://github.com/OpenLMIS/openlmis-contract-tests/blob/master/README.md (Contract tests - Concrete example section) 

  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-5752

•  Fix broken performance tests (those that give errors - don't push any changes to production code unless they have been approved)

  Jira Legacy
  server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-6118

•  

  Jira Legacy
  server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-6571

•  

  Jira Legacy
  server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-6578

•  

  Jira Legacy
  server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-6579

•  Update Fulfillment Process and Statuses (also add notifications)
•  Create new or update Stock Management workflow
•  Upgrade Jenkins to latest stable LTS version and update plugins that report security vulnerabilities 

  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-5741

•  

  Jira Legacy
  server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5728

•  

  Jira Legacy
  server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5743

•  Add new tests (no need to commit to branch), manage and add tickets for missing tests 
  1. contract tests –  OLMIS-1012 - Contract tests for implemented features TO DO
  2. performance tests -  OLMIS-3623 - Reference Data Performance TO DO
  3. functional tests -

     Jira Legacy
     server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5496

     Jira Legacy
     server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5495

     Jira Legacy
     server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5497

      

     Jira Legacy
     server System JIRA serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-5716

•  Groom the TechDebt backlog by first prioritizing in the issue list, and then by ranking them on the board (more details on Dev Group)
•  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.
•  Quick win tickets – https://openlmis.atlassian.net/issues/?filter=20549 (take by priority - from top to bottom, commit to branch if necessary)
•  Fixing tech debt  – https://openlmis.atlassian.net/issues/?filter=20544 (take by priority - from top to bottom, commit to branch if necessary)
•  Refining backlog bugs
•  Reproducing bugs that can only be verified on perftest or locally - OLMIS-5747.