The FOLIO project has adopted these types of tests for all code developed:

Type of Test	Automated/Manual?	What is tested?	What is accomplished by this testing? Why are we doing this?	How is this type of testing related to the other types of testing?	Who is responsible for making sure the tests are created/maintained/run?	What is due, when?
JUnit	Automated	Back-end unit tests			Devs have been writing these tests fro the beginning of the project.	Done, but perhaps some are not as complete as they should be.
RTL/Jest	Automated	User interface unit tests			Devs need to write tests for new functionality as well as convert the old BigTest tests. Good approach is for Lead PO for team to create JIRAs and bring several into each sprint (from KG). See sample SPIKE issue at UIEH-980 - Getting issue details... STATUS for example. Also see wiki page at https://folio-org.atlassian.net/wiki/x/zCMV, github page at https://github.com/folio-org/ui-eholdings/pull/1251 and feature UXPROD-2938.	Must be fully converted to Jest by September 30, 2021. Minimum is 80% coverage. Anton has created FAT- JIRA issues for apps.
Karate	Automated	API Integration		Overlaps with "end-to-end" tests.	POs need to determine what should be tested. Devs will create/maintain tests.	Anton has set a deadline of R2 2021. Anton has created FAT- JIRA issues for apps.
BigTest/Cypress	Automated	End-to-end tests	Test using browser to emulate what a user does–follow user workflows. Helps us to confirm that critical workflows are working properly.	Overlaps with "api integration" tests.	POs need to determine what should be tested. Devs will create/maintain tests.	Anton has not set a deadline for this yet.
Test Rail - BugFest	Manual	Everything			The Test Rail Test Cases are created and maintained by the appropriate Product Owner.
Test Rail - Smoke Tests	Manual	Critical functions	The purpose of this test is to insure that recent, post-BugFest changes have not impacted critical FOLIO functionality.

Browser not supported