Best Practices in Test Strategy during parallel developments
Many a times in order to reach market with the greatest and latest version of SAP solutions, the applications are built in parallel consuming the framework which itself under development.
How to ensure that the development is done without disruption?
When the suite systems are supplied with the NW week stones, one issue can disrupt the entire suite landscape and affect the entire development / Test activities. In order to avoid the same NWIQ (Net weaver Input Qualification) tests are held. In a nutshell, NWIQ is collecting the net weaver developments / corrections on a separate central landscape and executing a high level test to identify any critical issues. If there are issues then the particular week stone will be rejected and we will wait for the solution. If there are no issues the same will be made available for all suite landscapes which will not hamper the development activities and also will enable to develop on the latest version.
How do we ensure that the product in the market and the product being developed works seamlessly across various NW releases?
Basically it is very difficult to maintain the landscape for all permutations and combinations of various releases due to high maintenance and hardware cost. This is effectively addressed via the min / max strategy.
Maintaining the minimum version of the NW hubs (PI, Portal, BI, TREX, ADS, BWA (BIA), BOBJ Information Steward / DQM, Gateway etc.) that are delivered to the customers in the development landscape and keep on upgrading the test system to the latest version of the NW hubs ensures that our application works with the base release and also with the greatest release available in the service market place.