Skip to main content

Division Testing

Division testing (DT) is an optional testing stage carried out with ABB divisions (e.g., PAEN, PAPI, PADI) during the project if it is relevant to the respective product or system release.

DT is also known as enhanced testing. It focuses on planning and executing customer tests that are not covered by other R&D test stages. Test scenarios include, but are not limited to, the following deployment types:

  • Updates
  • Greenfield.
  • Division library integration.
  • Division-specific application engineering.
  • Specific performance and capacity testing.

DT is carried out either by agile test teams hosted in R&D or by teams in PA divisions, depending on the scope and coverage of the testing needed for the respective product or system release.

Intended for​

Test leads, test engineers, product owners, and release owners.

Identifying the need and planning for DT​

The team, consisting of release and product owners (also on system level in case of promoted brand releases), system and product test leads, and quality representative, should discuss with the division team to determine whether DT is required for a specific release project. If DT is required, the primary objective of DT should be identified prior to G2.

The DT phase should be aligned with the project schedule and merged with the release plan, common test strategy, and project test plan for tracking and monitoring purposes. The minimum details to be included and agreed upon by all stakeholders and participants are listed below. The details can be drafted for individual projects before G2, depending on the release project specifications.

  • Objective of DT.
  • Scope of DT.
  • RACI for DT.
  • Deliverables and KPIs for DT, e.g., test reports and defect classification.
  • A detailed plan for DT includes schedule and infrastructure requirements.

Recommendation: The ideal phase to start the DT is after a successful product or system beta qualification by product/system test. However, the scope, planning, and detailing of test cases should be done earlier in the project between G2 and G3.

Governance of DT​

DT should be monitored and governed as part of the regular project activities. The details can be planned by the team/s responsible for the DT along with the release owner based on the scope of the release and DT. Governance and coordination members from the PA division side and PCP side should be identified for the specific project. Typically, the release owner(s), product owner(s), and the division test leads / representatives should be members of the governance team. Other roles can be included if needed.

The DT team must be provided with a detailed description of the milestone delivery plan for their planning. Typically, a demonstration of new features or changes should be planned before delivering the build/software version to the DT.

Once the deliverables and schedules are defined and DT is in progress, a weekly/bi-weekly sync between the relevant R&D team (release owner(s) / product owner / system test team / product test team) and DT team should be planned to monitor test progress, defects investigation, posting plans, etc. A regular update from the DT should be made available to the program steering committee (SteCo) by identifying a DT coordinator directly or via the release owner as part of the regular project/program SteCo meetings.

Outcome and conclusion of DT​

DT should maintain and provide the test results like all other test stages defined in the R&D processes and should make the test reports, test conclusions, defect summaries, etc., available as required by the project team.

Upon completion of DT, the DT lead must make a release conclusion with the R&D team and deliver a final test summary with release recommendations.

Documentation and checklist for DT​

All the deliverables from DT, such as test plans, test cases, checklists, and entry and exit criteria, should use the artifacts and templates as defined in the R&D processes. Any specific documentation or checklist needed for DT should be tailored for the specific product or system release.

Owner: Test Team