James A. Whittaker Principal Architect Visual Studio Team Test Microsoft blogs.msdn.com/james_whittaker.

Slides:



Advertisements
Similar presentations
Test process essentials Riitta Viitamäki,
Advertisements

Test Automation: Coded UI Test
Acceptance Testing.
Evolution of the Storage Brain Using history to predict the future Larry Freeman Senior Technologist NetApp, Inc. September 6, 2012.
HP Quality Center Overview.
Engineering Secure Software. The Power of Source Code  White box testing Testers have intimate knowledge of the specifications, design, Often done by.
04b | Manage Test Execution (2 of 2) Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM.
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
Mike Azocar Sr. Developer Technical Specialist Microsoft Corporation
Slide 1.1 © The McGraw-Hill Companies, 2002 Object-Oriented and Classical Software Engineering Fifth Edition, WCB/McGraw-Hill, 2002 Stephen R. Schach
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.
Acceptance Test Planning. Business challenges Unclear requirements Delivered software does not meet value expectations Late-breaking changes and churn.
CSC230 Software Design (Engineering)
Remedy, a BMC Software company Storyboarding the User Interface: Blueprint for an Application Shanaz Kanga | Michele Sarko Sr. UI Design Engineer | Manager,
Overview of Lean Six Sigma
The #1 Easiest, Affordable & Most Powerful Business Process Modeling Software.
Terms: Test (Case) vs. Test Suite
11 Games and Content Session 4.1. Session Overview  Show how games are made up of program code and content  Find out about the content management system.
SOFTWARE ENGINEERING1 Introduction. Software Software (IEEE): collection of programs, procedures, rules, and associated documentation and data SOFTWARE.
What is Software Testing? And Why is it So Hard J. Whittaker paper (IEEE Software – Jan/Feb 2000) Summarized by F. Tsui.
Sri Lanka Institute of Information Technology Software Engineering Project – I Clone of Rally GROUP NO : WD-SEP-002 | PROJECT NO :25 PROJECT : CLONE OF.
1 Today’s Plan In Class Exam – Quick Review Thoughts on your Junior Projects, cntd People and Roles on Projects.
Testing Workflow In the Unified Process and Agile/Scrum processes.
@DNNCon Don’t forget to include #DNNCon in your tweets! Effective Unit Testing for DNN James McKee Solutions Developer / Enterprise
Introduction to Software Testing. Types of Software Testing Unit Testing Strategies – Equivalence Class Testing – Boundary Value Testing – Output Testing.
From Quality Control to Quality Assurance…and Beyond Alan Page Microsoft.
DEV322 Unit Testing Best Practices With Visual Studio 2005 Team System Mark Seemann Senior Consultant Microsoft Consulting Services.
James A. Whittaker Principal Architect Visual Studio Team Test Microsoft.
DEV 301 Visual Studio Team System Tom Arnold Program Manager Microsoft Corporation “Enabling Better Software through Better Testing”
WEP Presentation for non-IT Steps and roles in software development 2. Skills developed in 1 st year 3. What can do a student in 1 st internship.
Developer TECH REFRESH 15 Junho 2015 #pttechrefres h Understand your end-users and your app with Application Insights.
Turning Software Projects into Production Solutions Dan Fraser, PhD Production Coordinator Open Science Grid OU Supercomputing Symposium October 2009.
SOFTWARE ENGINEERING1 Introduction. SOFTWARE ENGINEERING2 Software Q : If you have to write a 10,000 line program in C to solve a problem, how long will.
James A. Whittaker Software Architect Visual Studio Team Test Microsoft
Anubha Gupta | Software Engineer Visual Studio Online Microsoft Corp. Visual Studio Enterprise Leveraging modern tools to streamline Build and Release.
EMEA Beat Schwegler Architect Microsoft EMEA HQ Ingo Rammer Principal Consultant thinktecture
Virtually Agile Astro Sabre (Matt Ganis) IBM, Senior Technical Staff Member Hawthorne, NY - September 20, 2007.
Prototyping. Outline Risk Management Prototyping Kinds of Prototypes Example Activity 1.
28. Januar, Zürich-Oerlikon. Working with Virtual Test Environments Marc Müller Principal Consultant 4tecture GmbH.
Visual Studio 2005 Team System: Enabling Better Software Through Testing Tejasvi Kumar Technology Specialist - VSTS Microsoft Corporation
MTA EXAM Software Testing Fundamentals : OBJECTIVE 6 Automate Software Testing.
Introducing Visual Studio 2010: What It Is and Why You Should Care
INFO 344 Web Tools And Development CK Wang University of Washington Spring 2014.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
Test Driven Development Introduction Issued date: 8/29/2007 Author: Nguyen Phuc Hai.
Team Skill 2 Understanding User and Stakeholder Needs Storyboarding (13)
Connect with life Tejasvi Kumar Developer Technology Specialist | Microsoft India
Successful Software Practice How to successfully work as a team to create software Chris Mendes, Chief Technology Officer Sirca Limited March 2012.
DEV300 Project Management And Visual Studio Team System Lori Lamkin Group Program Manager Visual Studio Team System.
Automation Testing Trainer: Eran Ruso. Training Agenda Automation Testing Introduction Microsoft Automation Testing Tool Box Coded UI Test and Unit Test.
Outcome Agile Testing. 2© 2010 OutSystems – all rights reserved How do you ensure the quality of your delivery?
Ognjen Bajić Ana Roje Ivančić Ekobit Efficient Application Testing.
Building Enterprise Applications Using Visual Studio®
Automation.
Azure Machine Learning
Tracking and Squashing Bugs
Computer Programming (BCT 1113)
Manual testing of Windows Metro style apps built using HTML
Defining Processes BEFORE ERP
Software Engineering D7032E
Tacit Codification An EmpFinesseTM Wisdom Modernization Solution.
Design and Programming
An Introduction to Software Architecture
Your code is not just…your code
What is Software Testing?
Vinod Malhotra Group Program Manager Microsoft Corporation
White Box testing & Inspections
Your code is not just…your code
Presentation transcript:

James A. Whittaker Principal Architect Visual Studio Team Test Microsoft blogs.msdn.com/james_whittaker

to err is HUMAN

nothing is PERFECT

WE all make MISTAKES

IT could have happened to ANYONE

We have many expressions to capture the fact that humans are fallible

Our creations and inventions echo this unnerving tendency

to FAIL

if there was an Olympics for FAILURE

Or a World Cup for that which sucks

surely SOFTWARE would reign supreme

Software … … stocks supermarket shelves … delivers electricity and water … stores our personal information … runs nuclear power plants … controls doomsday weapons …

Are these failures typical? How many of you have seen software fail? How many users share this same experience?

Any reason to think things will improve? Let’s take a look at the future and find outfuture

How will we test the applications of tomorrow?

Virtualization Information Visualization

Virtualization Information Visualization

Virtualization

Users are effective testers Let’s leverage their power – They have the environments we seek – They have the data we lack – They run the tests we don’t think of “Crowd-sourcing” is one answer I like Virtualization is the next step

Virtualization The story today: – A user (or tester) finds a bug, developer can’t repro it – A tester wants to reuse test cases, but can’t get them to run Virtualization solves this – User creates a VM at the point of failure These VMs have a market value Developers could have access to the sum total of all the environments in which their application can run – A tester creates VMs for every test suite We now have reusable, fully transferable testing assets An automated historical record of all testing on our app If we can store every video in the world, why not every test case/test data/user environment? – It’s not been possible before but it is now

Virtualization What does the virtualized testing world look like? – Think crowd-sourcing on steroids – Test VM’s have great value, businesses emerge owning and managing these environments – Testers analyze an app, license the appropriate Test VM’s, conduct the test and report results Companies no longer need QA departments Why test a subset of possible usage when (in the future) we can test them all? Software is important, it deserves this kind of coverage

Virtualization Information Visualization

Virtualization Information Visualization

Information

Information about me (Status, Health, etc.) Quick Access to oft- used abilities. Information about my target. Information about my location in the world.

Information What is the information we need? – Architects see Visio diagrams and flow charts – Program Managers see PowerPoint decks and Word storyboards – Developers see Visual Studio – Testers see binaries and interfaces In this model, testers see only what the user sees … I object!

Information What the user sees What the tester sees

Information Testers need more information – The architecture, design, code … they are all useful to testers in the right context – I want to hover over a UI element and see code, data types, value ranges, previous bugs, test history … – ‘Cheating’ is not wrong when you are trying to build a great product!

Virtualization Information Visualization

Virtualization Information Visualization

Well, there’s: – Input – Output – Data flow – Control flow – Modules – Dependencies – Environment variables – Files – Interfaces – Bugs Visualization

Software will continue to run our economy, our businesses and our lives Software will be a critical part of the solutions that will grow food, cure disease and produce sustainable energy Remove software from the equation and humankind’s problems get a lot harder It is imperative that we get software right!

20 years from now – Software testing will look fundamentally different – The tools will be more powerful and allow us to be more impactful – Software testers will contribute more fundamentally to the development process

20 years from now – Will the quality of software be taken for granted? Will users be genuinely surprised when it fails? – Will researchers look back in wonder that there was ever even a need for dedicated bug finders? – What hard problems will simply cease to be hard because the software industry of this time did what needed to be done?

James A. Whittaker, PhD Blog: blogs.msdn.com/james_whittaker URL: msdn.microsoft.com/testercenter