Test Resouce Allocation

Testing TypesTools/ Frameworks usedResoucesRemarks
Unit TestingJasmine, Karma

FE -Panos, Roope, Ola

BE- Simon, Jayant & other BE devs 

The most extensive coverage of test cases

Need to be in depth, defects identified at this stage have the least technical debt to fix.

Component/ Contract TestingPact, Cucumber


BE- Simon, Jag & other BE devs

DevOps - For Test Pipeline 

Shivani - Strategy, Planning and Review


Security TestingOWSAP security testing using ZAP

Shivani and one dev as backup

Devops - for initial setup


Integration TestingCucumber with Spring-boot

ESR - Jag, Ashley and Shivani

Other interfaces strategy  needs to be created for integration testing after co-ordination with BE devs

Post that resources will be allocated

DevOps -  For Test Pipeline setup

Shivani - Strategy, Planning and Review


E2E Testing

Cucumber with Protractor (BDD) 

Jasmine with Protractor (Regression)

Functional testing ( BDD ) -  Ola , Roope

Regression Maintenance  - Shivani / any FE dev

DevOps -  For Test Pipeline

No new functionality will be implemented  in Regression

Shivani - Strategy, Planning and Review


UAT ManualPO/ BA
Performance TestingJmeter or Gatling

BE Dev and Shivani (Testing will be more around ETL, Rest API and Interfaces), FE.

DevOps -  For Test Pipeline

Shivani - Strategy, Planning and Review


Post-Go-Live Validationse2e test pack

Shivani (Subset of e2e testing will be running against Production on demand)

PO/BA for early feedback

DevOps -  For test Pipeline and test data deletion