Testing

The Ignition testing team is an in house testing team that tests the work developed by the internal development teams. The testing team adapts the Agile Methodology and all work allocated to the team should be allocated to a sprint  User Story  Task.

All work needs to accompanied with a scope of work (i.e User story definiation ,BRS, Technical Specification , Flow diagrams) The team will draw up their plan based on the scope provided.

We offer a wide range of testing capabilities

• Api testing
  • Website testing
  • Compatibility
• Functional testing
• Micro service testing with Cypress Test automation
• Full Integration testing
• Automation testing
• Cypress
• Selenium
• System testing
• Full end to end testing of COTS and In house development
• Regression testing

The flow

1. When a ticket is ready for testing , Developer or Tester deploys to an available test environment(T1,T2,T3). Developer moves the ticket to testing on Azure Devops.
2. When a tester finds bugs they will log issues on Azure Devops
   1. Developer to resolve bugs and move to resolved
   2. Tester retests resolved bugs and re-opens or closes as required.
3. When a tester finds bugs they will log issues on TFS
   1. Developer to resolve bugs and move to resolved
   2. Tester retests resolved bugs and re-opens or closes as required.
4. RC Branch (release candidate is created)
5. Branch is deployed to Staging environment (by testers)
6. Tester completes regression test
7. Deployments
   1. Request for change needs to be logged on Fresh service and necessary approvals need to be granted
   2. Silver Surfer – This is deployed by the testers after hours (8.30pm)
   3. International – dependent on operational time
   4. Tester to perform Smoke Testing upon deployment

** No deployments on a Friday except Hot fixes (this needs to be signed off by Russell Stather, Femi Baiyewu ,Bhavna Namlal or Stephanie Naik) **