We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byKarly Cranmore
Modified about 1 year ago
Click to edit Master title style nFocus Software Testing e-Innovation Centre Shifnal Road Telford TF2 9FT Tel: 0870 242 6235 www.nfocus.co.uk Notes MAY accompany this presentation, please select notes page view © nFocus Ltd 2009 all rights reserved. These materials can be reproduced only with nFocus’ official approval. Approvals may be requested via email – firstname.lastname@example.org Test Management Summit January 2010 Institute of Directors, Pall Mall London Sam Clarke - Principal Consultant nFocus Sam_Clarke@nfocus.co.uk Giles Davies - Developer Tools Technical Specialist Microsoft Giles.Davies@Microsoft.com How can I tightly integrate my testing into the Application Development Lifecycle?
2 Agenda Introductions Why are we testing? Coping with change Demonstration of how Visual Studio 2010 enables integration of testing focussing on change Workshop - critical success factors © nFocus Ltd 2010 all rights reserved
Why should we test software? To see if it works To make sure it’s secure To show it hasn’t damaged other things To see if it’s reliable In fact there are many reasons depending on your role and professional interest. To see if it performs OK To show we can manage it To ensure we can install it To see if it’s usable To debug my program Confirm we meet regulations You can assert that testing: 1.Reduces risk of failure 2.Increases confidence of success 3.Supplies key information Objective Get the right level of quality, at the right price, at the right time Testing is not just about debugging programs! IT Systems are likely to have faults and you can’t test everything SME Challenges Budget, skills, critical mass © nFocus Ltd 2010 all rights reserved3
Fundamentally testing and quality assurance helps protect the reputation of the application, the business, the people and the company 4 ReputationApplicationBusinessPeopleCompany So where does testing fit in? Delivery as promised Minimal disruption Reliability as expected Press Share price Morale Pride Low attrition Early adopters Increased market share Minimised disputes Cost of maintenance as budgeted Profit as expected © nFocus Ltd 2010 all rights reserved
Testing adds value by reducing the risk of bugs in production, increasing confidence of a successful deployment and delivering objective information on the state of the system and the process by which it was developed Risk ConfidenceInformation Best Value Not delivering business benefits Damaging existing systems Implementing an unreliable system Developed to plan Complete Meets requirements Quality acceptable Quality of the system Quality of development process Residual risks after testing Constraints of: Cost Skills Resources Time Testing is a balancing act © nFocus Ltd 2010 all rights reserved5
However to fulfil these objectives testing must be an integral part of the Application Lifecycle Management Process from start to end delivering appropriate information that is applicable to all methodologies. 6 ConceptDesignDevelopDeployMaintainRetire Information – Building the right thing and building it right Test What does this mean for the project? Confidence of success and reduced risk of failure © nFocus Ltd 2010 all rights reserved
To deliver best value and key information, testing must have a repeatable process which integrates with the project and covering analysis, design, preparation, and execution of tests. Incidents can be raised at any time. Test repository Incident management system Project management repository Requirements repository Detect and record Incidents IssuesRisksDefects Information on the quality application and the dev. process Input to test (requirements, design, system, etc) Business and technical functional and non functional, Analysis Design and Specify tests PrepareExecuteLog results But something is missing...... Independent of methodology Code repository Designing and prototyping Stabilising Designing and building © nFocus Ltd 2010 all rights reserved7
Information can be difficult to provide if each of the test, project and development repositories are delivered by separate systems. This can be most apparent when trying to find the impact of a code change. Where is the data? In the head! Office tools Open source Proprietary systems 8© nFocus Ltd 2010 all rights reserved Quality of the application Progress Quality of the process Impact of change RisksTasks Dependenc ies Issues Process defects Application defects TestsTest logsChanges Specificati- ions ManualsCode Requirem- ents User stories What if something changes? What about unforeseen effects? Changes Tests Test logs Impact of change
Change is pervasive it effects reliability and testing has to deal with the issue of retesting function that has been affected. You cannot retest everything on each build so choice of tests by impact analysis is vital. Change is inevitable Agile approaches embrace change Development using Continuous Integration is delivering a continuously changing application Can’t wait until end of development to run tests Ideally all passed functional and system tests need to be run again on each build Need to quickly know impact of a change Change affects reliability increasing risk of damaging our Reputation Logistically we can’t retest everything after every change Automated regression testing helps by allowing lots of tests to be rerun in a short time Choice of tests to rerun can be difficult 9 So what do we retest after a change? © nFocus Ltd 2010 all rights reserved
If the Application Lifecycle Management System is fully integrated it is easy to provide consistent information about the impact of a change allowing informed decision to be made on risk, schedule and cost. 10© nFocus Ltd 2010 all rights reserved Quality of the application Progress Quality of the process Impact of change RisksTasks Dependenc ies Issues Process defects Application defects TestsTest logsChanges Specificati- ions ManualsCode Requirem- ents User stories Single integrated repository Consistent customised reporting
In summary to understand which black box tests have been impacted by an application change can be difficult. Knowing which code has been exercised by which test makes regression testing a much more effective and efficient process reducing risk and protecting reputation. Problematic subjective judgments taken Unrelated repositories (excel word, code bases) etc. Unknown code coverage with black box functional testing If you don’t know where you have been how do you know to go there again? What we need is an easy method and toolset to allow us to list tests that need to be rerun on a specific build of the system. 11© nFocus Ltd 2010 all rights reserved
13 Features Code, unit test, build Fail Run smoke test and regression test Test error fixes and new function Report progress Update regression tests. Prepare next feature tests System test Errors Incremental development of the automated tests with constant rerunning of the test set increases confidence that the tested function remains intact and shows immediately if there are any adverse effects. Accept- ance test Production test Run regression tests update as necessary Which tests to run? © nFocus Ltd 2010 all rights reserved
Q&A Any questions before we move on to the workshop session Are you convinced that full integration of testing into the ALM process is necessary? 14© nFocus Ltd 2010 all rights reserved
Workshop objective is to share your knowledge and experience to understand critical success factors of implementing testing into ALM What do you see as your challenges in integrating testing into ALM life cycle in the following areas? Attitude to testing Application development and test process Application Lifecycle Management Tools Personnel - skills, Roles & Responsibilities, organisation structure Test management Reporting and metrics Test Environments and data © nFocus Ltd 2010 all rights reserved15
Workshop Critical Success Factors Rank the factors that MUST be fulfilled for success from previous lists Attitude ALM and process Test Technology (including ALM tools) Personnel and Organisation Test Management Reporting and Metrics Test Environments and Test Data 16© nFocus Ltd 2010 all rights reserved
17 nFocus Ltd Consultants Automation Specialists Test Managers Test Analysts Process Outsource Tools www.nfocus.co.uk © nFocus Ltd 2010 all rights reserved
Click to edit Master title style nFocus Software Testing e-Innovation Centre Shifnal Road Telford TF2 9FT Tel: Notes MAY.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Adapted from the IEEE Standard for Software Test Documentation Version: (n) Company Name Software Quality Assurance Plan Date: (mm/dd/yyyy) Copyright ©
Test process essentials Riitta Viitamäki,
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
Agile Testing with Testing Anywhere The road to automation need not be long.
1 © Quality House QUALITY HOUSE The best testing partner in Bulgaria.
Interoperability. What is testing? Where have we come from? Where are we now? Why is nFocus at MSAIC? Overview.
Copyright 2002, Medical Present Value, Inc. All rights reserved. Copyright © 2010 Texas Education Agency. All rights reserved. TEA confidential and proprietary.
Process Scoring 1Ineffective. Basics not in place. Major exposures. 2Tasks defined; Weaknesses identified; plans in place for improvement. 3Process.
Agile development By Sam Chamberlain. First a bit of history..
CBIIT Quality Assurance Process Preston Wood NCI CBIIT Government Quality Representative (GQR) January 2014 RS.
Dr. Tom WayCSC Testing and Test-Driven Development CSC 4700 Software Engineering Based on Sommerville slides.
APMG-International Webinar Integrating Agile into PRINCE2® Thursday 19 December 2013 / 13:00 GMT Presented by Melanie Franklin,
Every stage from phase DESIGN in Software Development Process will have “design document” especially in analysis and design phases. “Design document”
Regression Methodology Einat Ravid. Regression Testing - Definition The selective retesting of a hardware system that has been modified to ensure that.
Validata Release Coordinator Accelerated application delivery through automated end-to-end release management.
Documentation Testing. Approximately 10 to 25 percent of a system’s development and maintenance effort is put toward developing and maintaining documentation.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
Internal developer tools and bug tracking Arabic / Hebrew Windows 3.1Win95 Japanese Word, OneNote, Outlook
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
IT Requirements Management Balancing Needs and Expectations.
Copyright © Panaya Oracle ® E-Business Suite Testing: How to Get Your Business Users On-Board Amir Farhi Director, Product Marketing.
SQA COMPONENTS IN THE PROJECT LIFE CYCLE C HAPTER 8 Dr. Ahmad F. Shubita.
Software Testing Process By: M. Muzaffar Hameed.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CS 360 Lecture 3. The software process is a structured set of activities required to develop a software system. Fundamental Assumption: Good software.
Process Definition Document Overview. This document defines the standard MN.IT roles and responsibilities for managing release and deployment of normal.
1 Punishment Through Continuous Delivery If it hurts, do it more often…
Introduction to Software Testing Maili Markvardt.
© SMARTESTING 2011 – This document is the property of Smartesting. It may not be reproduced in whole or in part Cliquez pour modifier le style du titre.
© 2006, Cognizant Technology Solutions. All Rights Reserved. The information contained herein is subject to change without notice. Automation – How to.
Software Development Software Testing. Testing Definitions There are many tests going under various names. The following is a general list to get a feel.
CS4723 Software Validation and Quality Assurance Lecture 15 Advanced Topics Test Plans and Management.
Software testing basic. Main contents Why is testing necessary? What is testing? Test Design techniques Test level Test type How to write.
Copyright © 2014 ASTQB Presented by Rex Black, CTAL Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further.
Understand Application Lifecycle Management Software Development Fundamentals LESSON 3.1.
LECTURE 20 26/11/15. Summary - Testing ◦ Testing affects all stages of software engineering cycle ◦ One strategy is a bottom-up approach – class, integration,
Software Testing Testing principles. Testing Testing involves operation of a system or application under controlled conditions & evaluating the results.
Continuous Delivery and Team Foundation Server 2013 Ognjen Bajić Ana Roje Ivančić Ekobit.
1 TenStep Project Management Process ™ PM00.9 PM00.9 Project Management Preparation for Success * Manage Quality *
1 HP Quality Center Overview. 2 Deliver optimal business results through high-quality applications HP Quality Center core Supporting key stakeholders.
CO2403 and CO3808 – Quality Management Systems Quality process definition, administration and accreditation.
Software Testing. “Software and Cathedrals are much the same: First we build them, then we pray!!!” -Sam Redwine, Jr.
04b | Manage Test Execution (2 of 2) Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM.
Configuration Management. Why Is Software Difficult to Build? Lack of control Lack of control Lack of monitoring Lack of monitoring Lack of traceability.
Introduction Telerik Software Academy Software Quality Assurance.
Copyright © IRI, Confidential and proprietary. Expanding Your Training Outlook with E-Learning IRI eSuite See - Act – Win.
© 2017 SlidePlayer.com Inc. All rights reserved.