Pay Per Test Case (PPTC)

Transcription

1 Pay Per Test Case (PPTC) Jitendra Prabhakar Atale Infosys Limited ISQT s STEP-AUTO 2011: Conference on ERP Testing Page 1

2 Contents 1. Abstract Introduction Problem Statement Proposed Solution Future Direction Conclusion... 6 Appendices... 7 Appendix A References... 7 ISQT s STEP-AUTO 2011: Conference on ERP Testing Page 2

3 1. Abstract As the time and investment in testing continues to increase in ERP testing. It's need of time that there should be alternative solution for the conventional ERP testing. Idea is to develop ERP testing portal and upload the ERP testing work. Portal will assign work request number to customer for tracking purpose. Domain consultant will review testing work, assign the complexity level and submit back. If customer agrees to pay cost then portal redirects for online payment. Customer's business user tests the required functionality and finally closes this work request if satisfied. To conclude, it will reduce overhead of customer to maintain domain consultants team and it is applicable to all type of ERP applications. 2. Introduction Pay per test case (PPTC) is the only way of saving spending on Enterprise Resource Planning (ERP) testing/package Testing (PT). PT requires business knowledge to write down the business scenarios. Business scenario finally converts to business scripts or test scripts. PPTC guides you through the whole testing lifecycle. There is no Test Strategy and no explicit testing phase. Both are replaced by automated tests which are executed in iterations to ensure high application quality. Proponents of PPTC claim that it leads to faster testing and to more reliable test results. Also reduce IT infrastructure acquisition and maintenance costs. It will save significant time of business users. These are the few properties would make PPTC superior to the conventional testing which compromised of a detailed strategy, testing phase and test results. In this paper, we present as process model for the paying as per test case executed based on the functionality tested. This model is based on following assumptions. The testing with insufficient blueprints/requirements is slower PPTC leads to higher quality for testing Other aspects of PPTC, e.g. cost of portal development are not captured explicitly by our model as their impact on the monetary value of the project cannot be easily separated. Thus, we consider our model as first major step towards a full overall assessment of PPTC. ISQT s STEP-AUTO 2011: Conference on ERP Testing Page 3

4 3. Problem Statement Large corporations are becoming increasingly frustrated with the long deployment cycles, high costs, complicated upgrade processes and information technology (IT) infrastructure demanded by traditional software applications. Many are realizing that the future of IT is moving away from data center, system and infrastructure management and more toward business process improvement. 4. Proposed Solution PPTC delivers application quality management solutions in a flexible service model that accelerates the implementation and maintenance of your products, applications. PPTC delivers application testing services in a highly available, consumable, pay-as-you-go model that provides flexibility in service and pricing. It also lowers the cost of entry to full service testing options and helps you implement best practice quality management processes. And it helps you leverage your existing investments by incorporating them into your testing centre of excellence. PPTC portal is based on Testing as a Service (TaaS) methodology. Testing as a Service (TaaS) is cloud based testing framework. In this customer is signing TaaS contract with vendors from span of 1 to 3 yrs for continuous managed testing work in Fixed or T&M pricing model. In PPTC, evaluation of work is on the basis of Unit of Work (UoW) pricing model. The basic methodology of Unit of Work (UoW) pricing model for assessing and creating unit prices for different types of test cases involves the following steps: Test cases are categorized by type, e.g., batch testing, installation testing, etc. For each test case type the activities that comprise it, e.g., batch classification, scripting efforts, etc., are identified ISQT s STEP-AUTO 2011: Conference on ERP Testing Page 4

5 The effort required to carry out and complete each activity is then calculated to produce total effort estimation for each test case in question. Based on the cumulative complexity level of its constituent activities each test case is then assigned its own complexity level, from which its proposed baseline price is derived. The baseline price for a particular test case is applied to a single test/release cycle. For subsequent release/cycles the efforts would be reduced based on the lessons learned and productivity gained from the initial cycle Once requirements are received from client through PPTC portal, business domain consultant will do evaluation of work by UoW pricing model. Evaluation of testing work is sent back to client through , and also uploaded on to portal. If need arises to work along with IT team of client or development team of other vendor communication channel needs to set up by client. ISQT s STEP-AUTO 2011: Conference on ERP Testing Page 5

6 Once signed agreement is received online and payment has been made, test planning phase begin and end with execution of test cases once work has been deployed on test instance. Defects would be tracking through PPTC portal and require access would be provided to client and development team. End-to-End testing would be carried out with the help of dedicated technical resources available to reduce dependency on IT team or development team. Once final sign-off certification of testing would be issued with test results, PPTC team would help to client during UAT phase of client if signed agreement contains the condition of UAT support. 5. Future Direction Within portal we will implement pricing business logic on the basis of fixed price/t&m and UoM pricing models. It will save significant efforts of employees to enter in to Infosys Deal Pricing (DP) system separately. Also Automation would help to reduce the efforts of manual testing. Infosys Test Automation Accelerator (ITAA) can be integrated with the PPTC for the value adds to customers. 6. Conclusion While Software as a Service (SaaS)/Platform as a Service (PaaS)/Testing as a Service (TaaS) will continue to thrive in cloud based technology, PPTC based testing model has the potential to deliver quality testing solution. Also PPTC would further optimize outsourcing costs. This model have would assist the clients to bring in their IT infrastructure cost down and consume resources according to need while reducing ad-hoc and unplanned requests. PPTC would provide one-stop access to a comprehensive and structured test service, including tools and environments and on demand test service as a single service or embedded in long term service contract Client can also have competitive pricing model on pay-per-test case and fixedprice basis. This will further enable high quality test services provided by expert test resources using state of the art tools and standardized test processes. ISQT s STEP-AUTO 2011: Conference on ERP Testing Page 6

7 Appendices Appendix References White Papers Conceptual Alternative Approaches to Application Services Pricing. Realizing the Enterprise Test Automation vision About the Return on Investment of Test-Driven Development Software as a Service ISQT s STEP-AUTO 2011: Conference on ERP Testing Page 7