UI Testing Team Request/Backlog Page

This page lists the requests and/or items that the technical council is reviewing.

1 Current Items:
2 Requested:
3 Prior/Completed Backlog:

NEW REQUESTS may be added directly to the "Requested" table, or the requestor can also reach out directly to members of the UI Testing Team.

Each inquiry should cover the following:

Item: In a very concise way, describe the problem that needs to be addressed.
Problem Statement/Background: Set context by describing the landscape surrounding the issue (history, technical components/versions, teams, etc.)
Interested Parties: Who will be impacted by a decision and if possible, what are their perspectives on this request.
Requested Action: What, specifically, are you asking the UI Testing Team to do?

Current Items:

Item	Problem Statement/Background	Interested Parties	Requested Action	Requested By	Request Date	Current Status	TC Lead

Item

Problem Statement/Background

Interested Parties

Requested Action

Requested By

Request Date

Current Status

TC Lead

UI Testing Spike

@Anton Emelianov (Deactivated)'s #1 observation was that there is a lack of guidelines related to UI Testing in the FOLIO project. This puts quality and productivity at risk.

Community, TC, PC

Assemble a task force to execute a spike to review testing tools, processes, etc. and to establish a set of guidelines. The outcome of this effort would be:

- UI Testing Guide, including specific tools, that will enable different teams to follow best practices in building UI unit tests.
- Sample tests
- Slack channel/community around development of UI tests

@Anton Emelianov (Deactivated)

July 18, 2018

Kick-off meeting being scheduled

delegated to @Anton Emelianov (Deactivated)

Insufficient build processes

@Anton Emelianov (Deactivated)'s #2 observation was that the build process is immature and/or fragile. Issue was described in https://folio-org.atlassian.net/browse/FOLIO-1335 https://folio-org.atlassian.net/browse/FOLIO-1338 https://folio-org.atlassian.net/browse/FOLIO-1043

Community, TC, PC

Research possible changes to improve reliability of packaging and distribution of build artifacts
Review existing component dependency management and recommend improvements
Implement triggering of automated tests based on dependency tree

@Anton Emelianov (Deactivated)

July 18, 2018

Core Team is working the issue

@Zak_Burke

Requested:

Item	Problem Statement/Background	Interested Parties	Requested Action	Requested By	Request Date	Current Status

Item	Problem Statement/Background	Interested Parties	Requested Action	Requested By	Request Date	Current Status
	Define SonarQube Quality Gate for UI modules
	Implementation of Pact tests

Once the Tech Council reviews the request and has enough information, if it is accepted into its current backlog the item will be moved into the Current Items table. If for some reason the TC decides to not pursue the request the decision will be documented in the following table.

Prior/Completed Backlog:

Item	Problem Statement/Background	Interested Parties	Requested Action	Original Request Date	Decision/Disposition	Completed Date

Item	Problem Statement/Background	Interested Parties	Requested Action	Original Request Date	Decision/Disposition	Completed Date