Page Comparison

...

This decision was migrated from the Tech Leads Decision Log as part of a consolidation process.  The original decision record can be found here.

RFC 

N/A

Stakeholders

@mention individualAnton Emelianov (s) who has vested interest in the DR. This helps us to identify who needs to be aware of the decision

Contributors

List individual(s) sposnoring/advocating for the decisionDeactivated)

Contributors

Aliaksei Chumakou Mikita Siadykh 

Approvers

This decision was made by the Tech Leads group prior to the adoption of current decision making processes within the FOLIO project.

Background/Context Explain the need that triggered the need for making a decision

Improving of testing process for FOLIO UI.

Current state

• No formal testing approach (it might be looking like a Tests Pyramid, but we don't actually work on E2E tests, only support existing)
• Tests are for coverage
• Some tests cover a lot of, but test nothing
• Some modules don’t meet acceptance criteria
• No defined toolset
• No manual testers (only BugFest phase, what sometimes looks not good for testing due it's limited time)
• Regression testing during quarter releases

Assumptions

N/A

Constraints

N/A

Rationale

N/A

Decision

...

To increase code quality/detect regression bugs on early stage.

Basically, we do have already DOD for tests coverage, so we can just formalize this for unit and integration tests, and check if we need to change testing tools on the upcoming meetings to provide more or less real coverage.

But for E2E tests we don't write any and if we formalize that in requirement (PO participation in what scenarios should be covered) - we can proceed with debating on tools as well on upcoming meetings. But it will be already a huge step forward for decreasing regressions, since they could be noticed even if something was changed in stripes-components, but ui-orders scenarios has started to fail.

Decision

N/A

Implications

• Pros
  • N/A
• Cons
  • N/A

...