Skip to content

Latest commit

 

History

History
32 lines (19 loc) · 2.41 KB

system-processes.md

File metadata and controls

32 lines (19 loc) · 2.41 KB

System Processes

In this space, you can find information on tickets, testing, release processes, and other Unity system wide processes.

Software development requires different levels of testing at each individual level fo the development lifecycle. Though the scope of the testing is different, it shall always be automated where possible.

Rules

  1. All software is tested
  2. All tests are automated
  3. Only 'released' code can go to the Test environment
  4. Only tested releases in the Test environment can go to Production

Unity Development Environments

EnvironmentOwnerDescriptionGateTenant Accessible
DevelopmentDev TeamsEnvironment for the initial and continued development of a unity software componentUnit testNo
Software Integration and Test (SIT)Dev team leadsEnvironment for the integration between components of the Unity system (across service areas)Unit Test
TestPSE/I&TEnvironment for mature components and formal testing of the entire system before release to productionIntegration testsNo
ProductionPSEProduction environment for the Unity platformSystem Release TestingYes

Test Plan and Procedures

  • Service teams own all unit and 'integration' testing within their service area
  • unit and integration tests shall all be automated and run on checkin and/or deployment
  • PSE will own the test plan for the TEST environment
  • Development Teams/Service areas own the test procedures/executions for the TEST environment
  • Test plan will focus on system level testing exercising the standards based interfaces, not the underlying implementation, that is, it should test the WPS, not ‘HySDS’.

These 2 items ensure that a certain level of validation is occurring at the system level while not blocking development teams. This work has to be synergistic.

The test plan will be derived from Epics and requirements, and will focus mainly on 'functional' requirements.

Test procedures should be automated wherever possible in order to minimize the time from release to tested to operational deployment. The goal should be to remove any person or role from those steps where possible.