Acceptance Testing
-
Upload
rosman -
Category
Technology
-
view
385 -
download
2
description
Transcript of Acceptance Testing
2
IntroductionTesting FocusTesting ApproachTimeQuality ControlMajor RisksSuccesses and Failures
3
Objectives of today’s presentationBackgroundProjectsExperience
4
Business Acceptance Testing◦ People
Organisational Structure◦ Process
Procedures, control, monitoring and risk management◦ Technology
Data integrity, system functionality, connectivity and communications
5
Which testing approach? Combined Functional and User Acceptance Testing Model Office
◦ Intuitive (error guessing)◦ Alpha◦ Beta
All or some Which method? Requirements based Risk based
6
Statement:- ‘Testing is often a matter of Time and/or Cost against Quality’
Suggested Points of discussion:- Quality and Time Quality and Cost Quality, Cost and Time Mitigating Risk
7
CAN WE START ACCEPTANCE TESTING? ARE WE READY?
Current Status in project lifecycle Status of Planning and Scripting documentation Has a risk assessment workshop taken place? Have the procedures been written? If previous testing phases have completed did they pass the exit and entry criteria? Has the exit and entry criteria been fully defined? Have the operational procedures been written Have the service level agreements been finalised? Has the planned test process (all phases) been agreed, reviewed and signed off. Are the required number of resources in place? Is the environment available and is it fit for purpose? Is there still enough time left in the plan to adhere to the test strategy Has any training of the Business Testers taken place? What is the status of any Third Party deliveries or internal dependencies?
8
Testing Quality Control is not just about testing the Software or the Business processes it is
about:- Reviewing the testing process and method The Testing Governance Audibility and visibility Documentation controls Auditing Third Party Deliveries Does the exit and entry criteria match the Business expectations
“ARE WE GETTING WHAT WE WANT FROM TESTING?”
9
Test environment unavailable
Ambiguous Requirements or Specifications
Test Strategy is unworkable
Exit and Entry criteria has not been fully defined
Late delivery of code
Quality of Delivered code
Exit and entry criteria for previous test phases have not been met
Absence of accurate planning and preparation
Lack of skilled resources
Overlap of test phases
Insufficient Coverage
Thorough risk assessment has not been carried out
Poor configuration management
Inadequate release management controls
Defect Management and change control processes are uncontrolled
Time
10
‘Things that go bump in the night’
Trying to test conversion data and functionality changes in the early stages together and in the same test environment.
Neglecting to ascertain all the set up requirements and all the necessary test data prior to commencement of testing.
Configuration of the test environment is nothing like live. Assuming that supposedly unchanged interfaces will still operate
when received by another system. Taking short cuts without performing a full risk assessment. Permitting unplanned code releases (fix and run). Ignoring Insidious faults Matrix Management
11
Barclays International – Global Co-operation Invesco – The pragmatic approach Barclays Global – Third Party success story Barclays – Planning paid off HSBC – No fall out