Test & perform QA - ERP Module setup, Interfaces, Workflows, Security, Customisation etc

1. Testing & Quality Assurance
ERP Modules, Interfaces, Workflows,
Security, Customisation etc
Anand Subramaniam

2. “I shall tell you a great secret, my friend. Do
not wait for the last judgement, it takes
place every day.”
- Albert Camus
2

3. Highlights
 Overview
 Process Roadmap
 Types of Testing
 Personnel Involved
 QA on Test Deliverable
 Testing Metrics
3

4. Test / QA – Overview

5. Testing - Requirement ~ Sign-off
Requirements
Report Plan
Status Test
Execute Create
Re-test Test
Resolve Execute
Errors Identify Test
Errors
5

6. QA Review - Requirement ~ Sign-off
Requirements
Report Plan
Status Test
Execute Create
QA Re-test QA Test QA
Reviews Reviews Reviews
Resolve Execute
Errors Identify Test
Errors
6

7. Test Methodology
Develop Test
Determine Test Obtain Test Develop Test Setup Test
Cases/
Strategy Resources Plans Environment
Procedures
Sign-off &
Execute,
Obtain Test Track, Resolve Assist with On-
Execute Test Retest,
Resources Issues / Risks going Test
Regression
Activities
7

8. Testing Types
Customise,
Conversion,
Regression Interfaces, User
Functional
Reports Acceptance
Integra- Testing Security
tion
Types
Perfor-
Unit
mance Stress / Workflow
Volume s
8

9. Test / QA – Process Roadmap

10. Test / QA – Process Roadmap
Establish
Requirements
Project Test Case
and Project Test Planning
Standards / QA Development
Scope
Method
Lessons
Quality User
System Learned /
Assurance Acceptance
Validation Continuous
Testing Testing
Improvement
10

11. Requirements & Project Scope
 Requirements are collected and analysed
 Requirement documented - reviewed,
finalised and agreed upon by all project
participants
 Testing scope of the project is established
and agreed upon
11

12. Establish Project Standards
 QA team will assist in establishing and
setting the standards for the project
 The standards established for:
 Development Methodology
 System Design
 Quality Assurance Methodology
 Methodology Compliance
12

13. Quality Methodology
 The QA team will establish Quality
Assurance methods, practices and
standards
 The overall QA methodology will assist in
creating a controlled product release and
greatly reduce the risk of errors being
introduced into the product
13

14. Test Planning
 QA Team will:
 Write the Test Plans which detail the QA
involvement for the entire project life cycle
 Develop test conditions based on the
business needs and business scenarios
 Implement a defect-tracking mechanism
14

15. Test Case Development
 Test cases written to test the scenarios
covered in the test conditions
 Review the test conditions and
subsequent test cases with the project
users
 Write test cases that will cover all phases
of the QA life cycle
15

16. Quality Assurance (QA) Testing
 QA normally consists of 5 types of testing:
 Unit Testing
 Functional Testing
 System Integration Testing
 Regression Testing
 User Acceptance Testing
16

17. User Acceptance Testing
 The testing of the entire application by the
end-users ensuring the application
functions as set forth in the system
requirements documents and that the
system meets the business needs
17

18. System Validation
 All systems should go through a validation
process
18

19. Types of Testing

20. Testing Types
UNIT FUNCTIONAL INTEGRATION PERFORMANCE
Individual Full Modular Cross Modular Stress and
Components Testing Testing with all Volume Testing
or Module Development &
Technical
Components
20

21. Testing Types
 Unit Testing
 Functional Testing
 Performance / System Integration Testing
 Regression Testing
 User Acceptance Testing
21

22. Unit Testing
 The testing of the application modules to
verify each unit (module) itself meets the
accepted user requirements, design and
development standards
22

23. Functional Testing
 The testing of all the application’s modules
individually to ensure the modules, as
released from development to QA, work
together as designed and meet the
accepted user requirements and system
standards
23

24. System Integration Testing
 Testing of all of the application modules in
the same environment, database instance,
network and inter-related applications, as
it would function in production.
 This includes security, volume and stress
testing
24

25. Regression Testing
 Testing each of the application’s system
builds to confirm that all aspects of a
system remain functionally correct after
program modifications.
 Automated regression testing tools is the
preferred method
25

26. User Acceptance Testing
 The testing of the entire application by the
end-users ensuring the application
functions as set forth in the system
requirements documents and that the
system meets the business needs
26

27. Personnel Involved

28. Personnel
 QA Manager
 Business Analyst
 Quality Assurance Analyst
 Technical Writer
 Instructional Designer/System Trainer
28

29. QA Manager
 Establishes and implements the QA
Methodology for the project’s quality
 Acts as the project lead liaison between all
project areas to ensure all areas are
completely and correctly engaged
 Oversees the entire QA Life Cycle and QA
staff
29

30. Business Analyst
 Writes the User Requirements and
Functional Specs and assists in writing the
system documentation
 Acts as a liaison between the QA Team
and the other project team members
 Assists in the QA test conditions
development
30

31. Quality Assurance Analyst
 Develops test conditions
 Writes test cases
 Performs Functional, Regression, and
System Integration Testing
 Assists in development of user guides and
training manuals
 Assists or performs the System Training
31

32. Technical Writer
 Assists in writing the user and system
documentation
 Maintains validation documentation
 Writes on-line help
 Writes the User Guide and Training
Manuals
32

33. Instructional Designer / Systems Trainer
 Assists in writing the user guides and
training manuals
 Trains users on production system
 Subject Matter Expert on Adult Learning
Theories and learning assessment
33

34. QA on Test Deliverables

35. Testing Documentation
 Test Strategy
 Test Plan Development
 Test Case Development
 Test Scenarios Development
 Test Metrics / KPI
 Internal Audit Reviews
 User Reviews
 Historical Information
35

36. Test Metrics

37. Testing Metrics
Metric Test Development Metrics Test Execution Metrics
Type
Functional  Number of requirements  Number of requirements verified
Metric allocated by test  % of requirements tested by each
 % of requirements by test business process (procure to payment,
development phase order to cash etc)
 Stability of server/platform per user
Problem  Problems tested for in  Problems found per business process
Metrics regression tests function
 Extreme conditions tested  Problems found per software component
for in functional tests  Number of critical/high problems found
per business process
Schedule  % completion of functional  Tests completed per functionality
Metrics test requirements by  Estimated number of days to complete
testing phase  Test cycle completion time
 Weighted functional  Time to complete testing per functional
requirement completion area
37

38. Conclusion
 QA’s involvement must be from the
beginning to the end of the project life
cycle.
 Properly managed, the QA process will
bring the system to production with cost
and time savings.
38

39. “When written in Chinese, the word crisis is
composed of two characters. One
represents danger and the other
represents opportunity.”
- John F. Kennedy
39

40. Good Luck
http://www.linkedin.com/in/anandsubramaniam
40