Making Software Testing Work Quality Assurance & Software Testing Methodology Presentation to...

of 15/15
Making Software Testing Work Making Software Testing Work Quality Assurance & Software Testing Methodology Presentation to JPMorganChase
  • date post

    30-Mar-2015
  • Category

    Documents

  • view

    217
  • download

    2

Embed Size (px)

Transcript of Making Software Testing Work Quality Assurance & Software Testing Methodology Presentation to...

  • Slide 1

Making Software Testing Work Quality Assurance & Software Testing Methodology Presentation to JPMorganChase Slide 2 Making Software Testing Work Contents What is ATS What is PLP Methodology Our Differentiators Accomplishments Benefits Why Amtex Recap What is ATS What is PLP Methodology Our Differentiators Accomplishments Benefits Why Amtex Recap Slide 3 Making Software Testing Work System Integration TestingApplication Integration Testing Engineering Testing or Quality Control Phase Business Testing or Quality Assurance Phase Testing Overview Slide 4 Making Software Testing Work ATS We work with & act as Business Users, while bringing a structured approach to testing. Our testing practice includes: Test Strategy Definition, Test Plan Creation, Test Case Writing, Test Execution and Certification that requirements have been met. With our proven onsite/offshore delivery model, Software Testing is a cost-effective approach to reducing ROI for clients. We work with & act as Business Users, while bringing a structured approach to testing. Our testing practice includes: Test Strategy Definition, Test Plan Creation, Test Case Writing, Test Execution and Certification that requirements have been met. With our proven onsite/offshore delivery model, Software Testing is a cost-effective approach to reducing ROI for clients. Slide 5 Making Software Testing Work ATS Testing Scope Business Testing under ATS is focused on two major issues though very often both are confused with same objective System Integration Testing System Integration Testing is focused on the technical infrastructure e.g. messaging, data flow, interfaces, and tools that are critical for applications and systems to work. Less stress on application functionality unless necessary. Application Integration Testing Also referred as Functional Integration Testing (FIT) Focused on application flow and functionality. Typically tested through a set of test plan / scenario each depicting a business process flow. Each plan / scenario may consist of several steps called test cases. Business Testing under ATS is focused on two major issues though very often both are confused with same objective System Integration Testing System Integration Testing is focused on the technical infrastructure e.g. messaging, data flow, interfaces, and tools that are critical for applications and systems to work. Less stress on application functionality unless necessary. Application Integration Testing Also referred as Functional Integration Testing (FIT) Focused on application flow and functionality. Typically tested through a set of test plan / scenario each depicting a business process flow. Each plan / scenario may consist of several steps called test cases. Slide 6 Making Software Testing Work System Integration Testing System Integration Testing is focused on the technical infrastructure like messaging, data flow, interfaces, and tools that are critical for application to work. Less stress on application functionality unless necessary. For smaller applications or where such points of testing are small in number or non-critical, then SIT can be merged with AIT for effective test resource utilization. The test strategizing involves identifying points of testing: Not every data flow is meant to be tested as application flow will test the data flow. The stress on data flow is through utilities and tools like an extractor, uploads from spreadsheet data, etc. Similarly in messaging, testing is done on whether formats are right, complete and message flows across modules / systems If there are tools used, then test the tools from their utility to application. In short, we need to identify points of testing without getting caught up with the entire application. We call this methodology Dot-The-Map. System Integration Testing is focused on the technical infrastructure like messaging, data flow, interfaces, and tools that are critical for application to work. Less stress on application functionality unless necessary. For smaller applications or where such points of testing are small in number or non-critical, then SIT can be merged with AIT for effective test resource utilization. The test strategizing involves identifying points of testing: Not every data flow is meant to be tested as application flow will test the data flow. The stress on data flow is through utilities and tools like an extractor, uploads from spreadsheet data, etc. Similarly in messaging, testing is done on whether formats are right, complete and message flows across modules / systems If there are tools used, then test the tools from their utility to application. In short, we need to identify points of testing without getting caught up with the entire application. We call this methodology Dot-The-Map. Slide 7 Making Software Testing Work Dot-The-Map methodology is developed uniquely by Amtex for System Integration Testing. Focus is emphasized on isolating the points of testing (Dots) that are critical for testing. A crucial criteria is whether such dots see the application as black box and vice versa or else the testing must be combined with AIT Examples, In applications that use MQ series messaging, testing message structure, flow, message servers. In applications that use SWIFT messages (MT 101, MT103), testing message formats, completeness and flow rather what application does with the messages when they come right. Testing tools e.g., a converter that converts EBCIDIC files to ASCII Dot-The-Map methodology is developed uniquely by Amtex for System Integration Testing. Focus is emphasized on isolating the points of testing (Dots) that are critical for testing. A crucial criteria is whether such dots see the application as black box and vice versa or else the testing must be combined with AIT Examples, In applications that use MQ series messaging, testing message structure, flow, message servers. In applications that use SWIFT messages (MT 101, MT103), testing message formats, completeness and flow rather what application does with the messages when they come right. Testing tools e.g., a converter that converts EBCIDIC files to ASCII Dot-The-Map Methodology Dot-The-Map Methodology Pick the critical points that tie the application together. Slide 8 Making Software Testing Work Methodology Check & Dig - The test plans and cases are written from a simple link (task) flow. For each link there are many combinations of flows. From domain knowledge, choose flows for testing that are different. If defect is found, choose more permutations & combinations. A selective and pragmatic approach to find errors and explore error zones. Each stage of testing - FIT, UAT, OAT - focuses on a select objective. Automated Testing tools like Win Runner, Load Runner and Test Director are used when the application is ready for a multiple roll out. Check & Dig - The test plans and cases are written from a simple link (task) flow. For each link there are many combinations of flows. From domain knowledge, choose flows for testing that are different. If defect is found, choose more permutations & combinations. A selective and pragmatic approach to find errors and explore error zones. Each stage of testing - FIT, UAT, OAT - focuses on a select objective. Automated Testing tools like Win Runner, Load Runner and Test Director are used when the application is ready for a multiple roll out. Task 3Task 2 Task 1 Business Process Flow All possible flows are identical in logic - Test one flow. 2 different logic in flows - Check both. Slide 9 Making Software Testing Work Key Differentiators Testing Methodology basics haven't changed, but applications have grown in size and technology complexity. ATS brings in unique PLP and Dot-The- Map methodologies for effective use of testing efforts. Amtex compliments technical depth with excellent domain knowledge by using Business Analysts to provide what is the right application perspective to testing. Automation testing is viable and cost effective and we have technical resource pool with automation experience on banking applications. We act like certifier than consultant. We dont merely execute testing services - We assure fit for use. Amtex has a matured process and methodology to offshore significant workload & bring down costs. Right Methodology is a critical success factor for for effective use of efforts. For Business applications domain expertise of team is a necessity. Automation is inevitable in most banking applications with multiple releases [Mercury / Rational / Compuware] Testing Business Applications is both about Is application RIGHT for use? and Is application working? We have effectively done test planning/scripting and execution offshore Slide 10 Making Software Testing Work Engagement Models PLP Methodology Engineering Testing and Quality Control Phase Business Testing and Quality Assurance Phase A complete 3 rd party testing of all phases post development ensures excellent cost savings as successive phases can leverage on knowledge gained on application Engagement in a any specific phase still gives the best of SakAssure - With Domain knowledge in FIT or Technical depth in OAT Slide 11 Making Software Testing Work Benefits We combine the requisite domain knowledge & technical skills to make business testing a success We compliment your team of business users and bring in structured & detailed testing process knowledge Our PLP methodology is efforts-effective We bring down costs with proven offshore model We have the necessary background and excellent credentials We combine the requisite domain knowledge & technical skills to make business testing a success We compliment your team of business users and bring in structured & detailed testing process knowledge Our PLP methodology is efforts-effective We bring down costs with proven offshore model We have the necessary background and excellent credentials Slide 12 Making Software Testing Work Deep domain skills Business Consulting Group Wide range of solutions spanning all segments of banking and retail lending Experienced software services company Full service provider of IT Outsourced solutions Custom Application Development Application Testing Staff Augmentation Extensive project management and technical capabilities Flexible, dependable, scalable and cost effective Committed to provide the highest quality ISO9001:2006 certified Quality Management System Deep domain skills Business Consulting Group Wide range of solutions spanning all segments of banking and retail lending Experienced software services company Full service provider of IT Outsourced solutions Custom Application Development Application Testing Staff Augmentation Extensive project management and technical capabilities Flexible, dependable, scalable and cost effective Committed to provide the highest quality ISO9001:2006 certified Quality Management System Why Amtex Focused Resource Slide 13 Making Software Testing Work Why Amtex Trusted Partners Information Builders Testing Methodology and Automation Functional Testing & Test Management Full testing Lifecycle myCove.com SDLC Development Testing Best Practices CITIGROUP Complete Testing Outsource for all Global Application Deployment HARRISONS GROUP Legacy Systems Conversion and Automation Slide 14 Making Software Testing Work Technology Labs Test Lab: Tools expertise on Mercury (Win Runner, Quick Test Pro, Load Runner, Test Director, Astra Load, Web Load), Rational and Compuware BI Lab: Data Warehousing & Business Intelligence products and tools expertise including Informatica, Oracle Warehouse Builder, SQL Server DTS, Business Objects, Hyperion, Cognos, MicroStrategy, SAS Base Technology Practice Java Practice: J2EE, JSP, EJBs, Servlets, JDBC, etc. Microsoft Practice:.NET, VB, VC++, COM/DCOM, IIS, MTS, ASP, etc. Mainframe Practice: MVS, CICS, Cobol, VSAM, DB2, CoolGen, MQ Messaging Other Skills: Cold Fusion, Power Builder, BPwin, etc. Extended Technology Groups Database Group: Oracle (including OLAP Services), MS SQL Server (including Analysis Services), Sybase, DB2, MySQL OS Group: Windows 2000, Unix flavors like Solaris, AIX, Linux, Mainframes & Macintosh Middleware Group: Web Sphere, Jrun, JBOSS, Oracle 9i Application Server, Web Logic, Pramati, Apache Data Modeling Tools: ERwin, Oracle Designer, Rational Technology Labs Test Lab: Tools expertise on Mercury (Win Runner, Quick Test Pro, Load Runner, Test Director, Astra Load, Web Load), Rational and Compuware BI Lab: Data Warehousing & Business Intelligence products and tools expertise including Informatica, Oracle Warehouse Builder, SQL Server DTS, Business Objects, Hyperion, Cognos, MicroStrategy, SAS Base Technology Practice Java Practice: J2EE, JSP, EJBs, Servlets, JDBC, etc. Microsoft Practice:.NET, VB, VC++, COM/DCOM, IIS, MTS, ASP, etc. Mainframe Practice: MVS, CICS, Cobol, VSAM, DB2, CoolGen, MQ Messaging Other Skills: Cold Fusion, Power Builder, BPwin, etc. Extended Technology Groups Database Group: Oracle (including OLAP Services), MS SQL Server (including Analysis Services), Sybase, DB2, MySQL OS Group: Windows 2000, Unix flavors like Solaris, AIX, Linux, Mainframes & Macintosh Middleware Group: Web Sphere, Jrun, JBOSS, Oracle 9i Application Server, Web Logic, Pramati, Apache Data Modeling Tools: ERwin, Oracle Designer, Rational Why Amtex Technology Breadth Slide 15 Making Software Testing Work Recap Amtex Systems Has: Domain knowledge Technical skills Credentials Methodology Cost Advantage To make Business Application and System Testing a Total Success. Glossary of Terms & Acronyms: PLP Process Link Probe AIT Application Integration Testing ATS Amtex Testing Service FIT Functional Integration Testing OAT Operations Acceptance Test SIT System Integration Testing UAT User Acceptance Testing ROI Return On Investment BR Business Requirement FS Functional Specification DD Design Document