Testing for change/Release Management

In a SAP support environment, the maintenance and support activities are regulated by the change management procedures defined in an organization. The changes would be released periodically as per release calendar to productive environments and should be tested and aprroved beforehand. The following testing would be applicable:

Integration testing for the changes:The changes as a part of chnage managment would be linked to the business process and the changed functionality can be tested quickly and comprehensively fo the end-to-end business process using automated testing. The test cases should be well defined for the objects or process that is to be tested. Custom Developments should also be covered with the required test cases as these are often chaged because os bugfixes or enhancement. This would result into faster turnaround of the changes.


Regression Testing:Regression testing is performed before the project go-live if it is rolling onto an existing productive system. The projcet go-live may require that a regression test may be performed by the already productive entities/countries/regions to ensure that their processes are not impacted by the new project or roll-out. Performing regression testing is a time consuming activity which can be automated. Automated testing would reduce the time span and would result into efficient and comprehensive testing.

Comments

Post a Comment

Popular posts from this blog

2.Areas of Deployment

Image
The below figure explains the systematic representation of the areas of deployment for automated testing:It is important to identify what part of the testing processes would be automated. The enterprise application, which are subjected to change either because of maintenance or project go-live, are most suitable for automated testing.
Read more

Setting Actions as Reusable Actions

Reusable actions are like functions in programming. When you have a process that you may need to include in several tests, you record, modify, and enhance the steps of the process and save them in a reusable action. Then you can call the action from other tests, rather than recording, modifying, and enhancing the same steps each time. To call an action from another test, you must make it a reusable action in the test with which it was stored. The Sign_in and ReturnHome action you created in this lesson can apply to almost any test you might create on the Mercury Tours site, so it makes sense to make them reusable actions. Make the Sign_in action reusable. In the Keyword View, right-click the Sign_in action and choose Action Properties. The Action Properties dialog box opens. Select the Reusable action check box and click OK. If a message box is displayed, read the message, click Do not show this dialog box again, and click OK. The action icon changes to a reusable action icon . ...
Read more

Sample QA/Testing Resume

QA Analyst  XXXXX(NAME),QA email@email.com XX Any Street XXXXXX XX 90000 (000) 000-0000 Senior QA Analyst with expertise in all phases of testing for client/server and Web applications SUMMARY OF QUALIFICATIONS Over "X" years of QA experience in all phases of life cycle, including requirements gathering, risk analysis, project planning, scheduling, testing, defect tracking, management, and reporting. Adept at using both manual and automated testing tools to troubleshoot systems, integration, user acceptance, positive and negative, functionality, object, and regression Develop use cases, user interface specifications, and user requirement specification documents. Liaise with developers, business analysts, and user representatives in application design and document reviews. Superior analytical, troubleshooting, communication and presentation skill. TECHNICAL SKILLS Testing Tools : QuickTest Pro, LoadRunner, Test Director, Visual Source Safe, Visual Intercept,...
Read more