PRACTICAL SOTWARE QUALITY AND TESTING 2008 Zpráva z konference Ing. Jaroslav Kalvoda (prezentace na pracovní snídani, čtvr...
Představení firmy <ul><li>Hlavní kompetence  </li></ul><ul><ul><li>Vývoj informačních systémů na zakázku </li></ul></ul><u...
Shrnutí PSQT 2008 <ul><li>Las Vegas, květen 2008 </li></ul><ul><li>Praktická a nekomerční konference </li></ul><ul><li>Šes...
Zdroje informací z konference <ul><li>Popis nejzajímavějších myšlenek z nejzajímavějších přednášek na následujících slidec...
Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><...
Luis Carlos da Silva <ul><li>GRID: Practical Experience of the Independent Software Test Group </li></ul><ul><ul><li>CESAR...
Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><...
Greg Stone <ul><li>From Ad Hoc Testing to Quality Assurance using Process as the Guide </li></ul><ul><ul><li>Iowa Foundati...
Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><...
Marina Gil-Santamaria <ul><li>How to Keep and Motivate Your QA Team without Increasing Your Budget </li></ul><ul><ul><li>T...
Myth #1:  “Anybody can do QA” <ul><li>Testing is a skilled activity that </li></ul><ul><ul><li>Requires the ability to thi...
Myth #2:  “Any out of school kid can test our applications” <ul><li>You systems/applications are critical company assets. ...
Myth #3:  “A QA Engineer is really a Developer Wanna Be” <ul><li>Some QA engineers DO enjoy coding BUT high performing QA ...
Myth #4:  “QA is a boring repetitive task with no creativity involved” <ul><li>This one could be true, it is up to you. Ho...
Myth #5:  “QA doesn’t provide much value to the organization” <ul><li>QA represents the heterogeneous users of the product...
Marina Gil-Santamaria <ul><li>How to Keep and Motivate Your QA Team without Increasing Your Budget </li></ul><ul><ul><li>T...
How to motivate your team <ul><li>Evaluate internal atmosphere   –do you see any of the 5 “myths” there? </li></ul><ul><ul...
How to motivate your team cont <ul><li>“ Brag” about your team   </li></ul><ul><ul><li>Come up with a list of periodic ach...
How to motivate your team cont <ul><li>Improve QA-development relations   </li></ul><ul><ul><li>Examine your own relations...
How to motivate your team cont <ul><li>Enhance your QA job descriptions   </li></ul><ul><ul><li>Take the time to put toget...
How to motivate your team cont <ul><li>Consider rotating projects and tasks   </li></ul><ul><ul><li>Be also respectful of ...
Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><...
Eric Newcomer <ul><li>Meeting New Challenges in Testing SOA </li></ul><ul><ul><li>Flat World Market Trends </li></ul></ul>...
Market Trends <ul><li>Companies have become virtual… </li></ul><ul><li>Blurred lines between company and supplier… </li></...
IT Transformation Challenges <ul><li>Applications are built not assembled </li></ul><ul><li>High-cost specialists </li></u...
Move From Monolithic Applications in Steps Intermediate stage:  Break out individual services Application Application serv...
Service Contracts Are the Key <ul><li>The key principles of SOA </li></ul><ul><ul><li>Services should be business-oriented...
WSDL: Typical Service Contract <ul><li>WSDL is very flexible </li></ul><ul><ul><li>Import existing WSDL contracts </li></u...
Pre-Certification Process Helps <ul><li>Early Collaboration and Validation </li></ul><ul><ul><li>Extends unit testing to i...
SOA: Interface Simulation and Testing <ul><li>SOA is based on interface contracts </li></ul><ul><li>Rapid Simulation Solut...
Building a Validation Framework System Test E2E  Test Unit  Test QA Testing Development Requirements Unit  Test Standard I...
Example: Time to Market Compression  PRODUCTION Def Dev Test Backend Billing Systems (eCare/Telegence) Middleware Tier (CS...
Example: Rapid Website Update <ul><li>.CO.UK business needed high-quality software  delivered at “Internet Speed” </li></u...
<ul><li>Reduce Cost of Correcting Defects </li></ul><ul><ul><li>Discovering defects one phase earlier saves $6,600 on aver...
Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><...
Lew Priven <ul><li>Software Inspection </li></ul><ul><ul><li>Identifikují chyby ve vývoj software již v době sběru požadav...
Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><...
Tony Simms <ul><li>Tips and Templates for Test Managers, Tony Simms </li></ul><ul><ul><li>Vytvořil a posbíral templates pr...
Test Strategy 
Reporting & Tracking Test Milestones 
Reporting & Tracking Test Milestones 
Reporting & Tracking Test Milestones 
Reporting & Tracking Test Milestones 
Reporting & Tracking Test Milestones 
Daily (weekly) Test Progress Reporting Click image above for template <ul><li>Simple, easy to complete daily or weekly rep...
Tony Simms <ul><li>Anatomy of a Test Strategy, Tony Simms </li></ul><ul><ul><li>Detailně popsal fáze testovacího projektu ...
Test Phases  [template section 6] <ul><li>Detail the relevant Test Phases for the project, a diagram helps visualise the s...
Work Products This diagram shows which Work Products are to be generated for each phase and activity.  Red bordered items ...
Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><...
Bill Miller <ul><li>Test Driven Quality  </li></ul><ul><ul><li>Vyjmenovává cíle testování </li></ul></ul><ul><ul><li>Ukazu...
Defect Severity <ul><li>Critical </li></ul><ul><ul><li>Loss of data, instability, and hazardous outcomes.. </li></ul></ul>...
Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><...
Patrick Freeman <ul><li>Software Quality Metrics for Critical Decision Making </li></ul><ul><ul><li>Uvádí sedm Software Qu...
Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><...
Shrnutí Headlines PSQT 2008 <ul><li>Testing Team Motivations by Marina Gil-Santamaria </li></ul><ul><li>Software Inspectio...
Poučení z PSQT 2008 <ul><li>Testovací tým </li></ul><ul><ul><li>Vylepšit atmosféru, prostředí - odbourání stresu, vyšší vý...
Poučení z PSQT 2008 <ul><li>Vztah TEST a TECH týmů </li></ul><ul><ul><li>Nutno popsat SLA mezi TECH a TEST </li></ul></ul>...
Poučení z PSQT 2008 <ul><li>Automatizace testů </li></ul><ul><ul><li>Vhodná pouze u regresního testu </li></ul></ul><ul><u...
Podrobněji o PSQT 2008 <ul><li>Popis nejzajímavějších přednášek v souboru PSQT 2008.doc (6 stran) </li></ul><ul><li>Podrob...
 
Upcoming SlideShare
Loading in...5
×

Practical Software Quality and Testing

450

Published on

Published in: Devices & Hardware
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
450
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Ok, so we have talked about the need to design services to support the business’s goals.   If we are moving from a non service enabled environment, how do we move toward an SOA in a sensible and controlled way?   The answer is to start thinking about monolithic applications as source material for services. Somewhere in the cookie dough of existing applications are nicely formed services wanting to get out. The job is to identify those services that fit general purpose requirements and that can be potentially reused by other applications. These can include redundant functionality (if the same function exists in multiple applications, it’s a great candidate for a service) or functionality that’s clearly needed by multiple applications, such as get customer record, lookup inventory, or calculate current interest rates or currency exchange rates.   Eventually once enough services are identified and carved out of existing applications, new applications can be created more and more by combining services.
  • The key to developing a good service, is a good contract. A contract allows the parties to a service (i.e. the requester and provider) to agree on terms and conditions, such as what messages will be exchanged and what data will be included in the messages. Well formed contracts also include quality of service requirements for reliability, security, transactions, etc.   Service contracts need to align closely with business services, as we’ve said.   Service interfaces must be clear, simple, and easy for any requester to understand (stay away from complex data types and structures, avoid execution environment specifics such as return codes, exception codes, or names.)   A good service contract is essential to achieve the primary goals of reusability and abstraction.
  • WSDL happens to be the best technology available for the implementation of service contracts. It separates the logical contract from its physical deployment, meaning that the definition of the data and the messages to be exchanged is separated from the physical format and protocol used to transport the message and data.   This allows multi-protocol and data formats needed in complex, heterogeneous environments.   WSDL is easy to create and manage. Import or create new, annotate with QoS (i.e. policy).
  • (This slide is optional for some audience. It’s purpose is to establish the broader context of SDLC/QA Solutions that we provide and how ISTF fits into that solution set).
  • (Build Slide) The typical problem IONA management consulting personnell see these days is that projects that are simply taking too long. SOA and other distributed techniques are allowing IT organizations to control costs by increasing re-use of assets and increasing the efficiency of increasingly specialized IT teams and providers. On the downside, it has created a situation where major projects are taking significantly longer. - Early proponents of SOA actually claimed it would be faster. But for large projects among the early adoprter this has simply proven not to be true. Like early assembly lines, early SOA adoptions have typically used a sequential model when it comes to project planning. The goal is now to find ways to do more work in parallel and save time. However doing work in parallel creates new risks and problems that must be resolved.
  • Pain – how do I manage so many development cycles Multiple projects to deliver, in this example trying to schedule 24 projects of varying complexity. Projects arise from marketing, applications, bugs etc Project managers need to own and deliver, scheduling like lining up the stars – very difficult, requires tremendous co-ordination and increasing pressure on test environment – hardware, software growth. ?And the business wants more,, functionality , applications, changes enhancements etct etc
  • If you pressed the power button on your car radio and it doesn’t turn the radio on, this would be a broken feature. If it finally worked every time after smacking it, that would be a work around. Would you want to own that car with that radio?
  • Practical Software Quality and Testing

    1. 1. PRACTICAL SOTWARE QUALITY AND TESTING 2008 Zpráva z konference Ing. Jaroslav Kalvoda (prezentace na pracovní snídani, čtvrtek 19.6.2008)
    2. 2. Představení firmy <ul><li>Hlavní kompetence </li></ul><ul><ul><li>Vývoj informačních systémů na zakázku </li></ul></ul><ul><ul><li>Data Management </li></ul></ul><ul><li>Řada dalších kompetencí </li></ul><ul><ul><li>Quality Assurance </li></ul></ul><ul><li>Přibližně 70 konzultantů </li></ul><ul><li>Přibližně 270 milionů tržeb ročně </li></ul><ul><li>Od 08/07 Oracle partner pro Českou spořitelnu </li></ul><ul><li>Od 11/07 součást rakouského New Frontier Holding </li></ul><ul><li>Quality Assurance </li></ul><ul><ul><li>Česká spořitelna </li></ul></ul><ul><li>Studie automatizované testy </li></ul><ul><ul><li>Česká spořitelna </li></ul></ul><ul><ul><li>Česká pojišťovna </li></ul></ul><ul><li>Testovací týmy </li></ul><ul><ul><li>Česká spořitelna </li></ul></ul><ul><ul><li>Česká pojišťovna </li></ul></ul><ul><ul><li>Vodafone </li></ul></ul><ul><ul><li>Sitronics </li></ul></ul><ul><ul><li>O 2 </li></ul></ul><ul><ul><li>IBM </li></ul></ul>Konference PSQT
    3. 3. Shrnutí PSQT 2008 <ul><li>Las Vegas, květen 2008 </li></ul><ul><li>Praktická a nekomerční konference </li></ul><ul><li>Šest souběžných tracků </li></ul><ul><ul><li>Test Process </li></ul></ul><ul><ul><li>Performance Testing </li></ul></ul><ul><ul><li>Test Management </li></ul></ul><ul><ul><li>Quality Management </li></ul></ul><ul><ul><li>Quality Management </li></ul></ul><ul><ul><li>Test Automation </li></ul></ul>
    4. 4. Zdroje informací z konference <ul><li>Popis nejzajímavějších myšlenek z nejzajímavějších přednášek na následujících slidech </li></ul><ul><li>Popis navštívených přednášek v souboru PSQT 2008.doc (6 stran) </li></ul><ul><li>Podrobné materiály k celé konferenci v souboru Welcome.jpg (1021 stran) </li></ul>
    5. 5. Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><li>Marina Gil-Santamaria, Testing Team </li></ul><ul><li>Eric Newcomer, Testing SOA </li></ul><ul><li>Lew Priven, Software Inspections </li></ul><ul><li>Tony Simms, Testing Templates </li></ul><ul><li>Bill Miller, Test Driven Quality </li></ul><ul><li>Patrick Freeman, Software Quality Metrics </li></ul>Magdy Hanna, PhD Conference Chair    
    6. 6. Luis Carlos da Silva <ul><li>GRID: Practical Experience of the Independent Software Test Group </li></ul><ul><ul><li>CESAR vývojové centrum při univerzitě </li></ul></ul><ul><ul><li>Dříve 200 test engineers rozptýlených po výzkumném centru nahrazeno 13 členy Independent Test Group </li></ul></ul><ul><ul><li>Vyvinuli metodologii pro odhad počtu test engineers na každý projekt </li></ul></ul><ul><ul><li>V týmu nemají rozdělené role (analyst, designer, manager…), nýbrž univerzální test engineers (senior) </li></ul></ul><ul><ul><li>Během nešpiček doporučuje využít tým na konzultaci business requirements a stimulaci developers </li></ul></ul>
    7. 7. Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><li>Marina Gil-Santamaria, Testing Team </li></ul><ul><li>Eric Newcomer, Testing SOA </li></ul><ul><li>Lew Priven, Software Inspections </li></ul><ul><li>Tony Simms, Testing Templates </li></ul><ul><li>Bill Miller, Test Driven Quality </li></ul><ul><li>Patrick Freeman, Software Quality Metrics </li></ul>
    8. 8. Greg Stone <ul><li>From Ad Hoc Testing to Quality Assurance using Process as the Guide </li></ul><ul><ul><li>Iowa Foundation for Medical Care </li></ul></ul><ul><ul><li>Asi 400 IT profesionálů, DWH asi 10 terabytes, kvartálně vyřizují 120 milionů claims, jejich SQA se za dva roky rozrostlo ze 45 na 100 lidí </li></ul></ul><ul><ul><li>Zpočátku testování prováděli Product Coordinators </li></ul></ul><ul><ul><li>Později zahrnuli SQA do každé části software life cycle </li></ul></ul><ul><ul><li>4 fáze SQA (Planning, Preparation, Execution, Wrap Up) </li></ul></ul><ul><ul><li>Netestují vše, klient ví co testují a co netestují a souhlasí se scopem </li></ul></ul>
    9. 9. Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><li>Marina Gil-Santamaria, Testing Team </li></ul><ul><li>Eric Newcomer, Testing SOA </li></ul><ul><li>Lew Priven, Software Inspections </li></ul><ul><li>Tony Simms, Testing Templates </li></ul><ul><li>Bill Miller, Test Driven Quality </li></ul><ul><li>Patrick Freeman, Software Quality Metrics </li></ul>
    10. 10. Marina Gil-Santamaria <ul><li>How to Keep and Motivate Your QA Team without Increasing Your Budget </li></ul><ul><ul><li>Tester jako „second class citizen“ (vs development) </li></ul></ul><ul><ul><li>Software bugs stojí US economy $59.5 billion ročně </li></ul></ul><ul><ul><li>Global s oftware t esting m arket byl $13 Billion v roce 2006 = 30% z total software development market (Gartner) </li></ul></ul><ul><ul><li>Uvádí 5 mýtů o testování a proč neplatí </li></ul></ul><ul><ul><li>Podrobněji viz dále… </li></ul></ul>
    11. 11. Myth #1: “Anybody can do QA” <ul><li>Testing is a skilled activity that </li></ul><ul><ul><li>Requires the ability to think, explore and follow logic while questioning and reasoning </li></ul></ul><ul><ul><li>Performed under time-constraints, with little or no documentation </li></ul></ul><ul><ul><li>Uses various types of infrastructure and experimentation, logic, models, mathematical probabilities and supporting tools </li></ul></ul><ul><li>Sorry, you just can’t take anybody off the street to do QA! </li></ul>
    12. 12. Myth #2: “Any out of school kid can test our applications” <ul><li>You systems/applications are critical company assets. If they go down or perform poorly </li></ul><ul><ul><li>Direct profit & revenue will suffer </li></ul></ul><ul><ul><li>Employee productivity will be affected </li></ul></ul><ul><ul><li>Support costs will increase </li></ul></ul><ul><ul><li>A company’s reputation can also be seriously damaged </li></ul></ul><ul><li>Would you hire inexperienced financial advisors to take care of your critical investments and financials assets? I didn’t think so! </li></ul>
    13. 13. Myth #3: “A QA Engineer is really a Developer Wanna Be” <ul><li>Some QA engineers DO enjoy coding BUT high performing QA teams need a variety of skills </li></ul><ul><ul><li>Domain expertise, communication, customer-facing, logical thinking to build end-to-end test cases , automation, etc </li></ul></ul><ul><li>QA teams develop the plan that will ensure the success of a company’s product in the marketplace! </li></ul>
    14. 14. Myth #4: “QA is a boring repetitive task with no creativity involved” <ul><li>This one could be true, it is up to you. How are your </li></ul><ul><ul><li>Internal processes and QA cycles that you have in place </li></ul></ul><ul><ul><li>On-going automation and new initiatives </li></ul></ul><ul><li>How involved is your QA team with customer interactions and product requirements? </li></ul>
    15. 15. Myth #5: “QA doesn’t provide much value to the organization” <ul><li>QA represents the heterogeneous users of the products that your company produces to </li></ul><ul><ul><li>Improve end-user experience, quality and reduce support costs </li></ul></ul><ul><ul><li>Think about all your DAILY responsibilities and tasks! </li></ul></ul><ul><li>Everybody “shoots” the messenger….BUT…How well are you communicating the information that is important to your stakeholders? </li></ul>
    16. 16. Marina Gil-Santamaria <ul><li>How to Keep and Motivate Your QA Team without Increasing Your Budget </li></ul><ul><ul><li>Tester jako „second class citizen“ (vs development) </li></ul></ul><ul><ul><li>Software bugs stojí US economy $59.5 billion ročně </li></ul></ul><ul><ul><li>Global s oftware t esting m arket byl $13 Billion v roce 2006 = 30% z total software development market (Gartner) </li></ul></ul><ul><ul><li>Uvádí 5 mýtů o testování a proč neplatí </li></ul></ul><ul><ul><li>Uvádí 10 způsobů motivace testovacího týmu, zejména </li></ul></ul><ul><ul><ul><li>Vylepšit atmosféru v týmu </li></ul></ul></ul><ul><ul><ul><li>Zlepšit vztah testovacího a vývojového týmu </li></ul></ul></ul><ul><ul><ul><li>Podrobněji viz dále… </li></ul></ul></ul>
    17. 17. How to motivate your team <ul><li>Evaluate internal atmosphere –do you see any of the 5 “myths” there? </li></ul><ul><ul><li>Take the time, act as “new” or a consultant on the job, and identify 1 or 2 areas for improvement </li></ul></ul><ul><ul><ul><li>For you: More knowledge of what are the team roadblocks! </li></ul></ul></ul><ul><ul><ul><li>For the team: Increase sense of appreciation and boost morale </li></ul></ul></ul><ul><li>Communicate, communicate and communicate with your stakeholders </li></ul><ul><ul><li>Understand what your stakeholders are measured on so you can report back what is valuable and important to them </li></ul></ul><ul><ul><li>Don’t be afraid of the business side! Report back on business metrics as well </li></ul></ul><ul><ul><ul><li>For you & the team: Demonstrate more value </li></ul></ul></ul> 
    18. 18. How to motivate your team cont <ul><li>“ Brag” about your team </li></ul><ul><ul><li>Come up with a list of periodic achievements from your team, and talk about them whenever you are interacting with your peers (status meetings, department Cross Functional meetings, etc) </li></ul></ul><ul><ul><ul><li>For you & the team: Demonstrate more value </li></ul></ul></ul><ul><li>Challenge your team: Explore automation and/or new testing initiatives </li></ul><ul><ul><li>Investigate first your own processes and past automation initiatives </li></ul></ul><ul><ul><ul><li>For you: Team will be more efficient, you will show results, you will look great with upper mgmt! </li></ul></ul></ul><ul><ul><ul><li>For the team: Learn & gain valuable skills, avoid repetitive tasks </li></ul></ul></ul> 
    19. 19. How to motivate your team cont <ul><li>Improve QA-development relations </li></ul><ul><ul><li>Examine your own relations and reporting structure as well </li></ul></ul><ul><ul><li>Come up with very specific goals (new cross-functional meetings, more team building exercises, etc) </li></ul></ul><ul><ul><ul><li>For you: More productive team, better collaboration, reflect very positively on you with upper management </li></ul></ul></ul><ul><ul><ul><li>For the team: More sense of appreciation & respect </li></ul></ul></ul><ul><li>Be a “good” manager </li></ul><ul><ul><li>Employees usually leave a manager not a company! </li></ul></ul><ul><ul><li>Show appreciation, coach & mentor, consider allowing telecommuting and/or flexible schedules </li></ul></ul><ul><ul><ul><li>For you: Employees will stick with your for the longer term </li></ul></ul></ul><ul><ul><ul><li>For the team: Fun, enjoyable working environment </li></ul></ul></ul> 
    20. 20. How to motivate your team cont <ul><li>Enhance your QA job descriptions </li></ul><ul><ul><li>Take the time to put together a more enticing job description </li></ul></ul><ul><ul><ul><li>For you: Simple </li></ul></ul></ul><ul><ul><ul><li>For the team: Shows that the company values their QA resources. </li></ul></ul></ul><ul><li>Involve QA in your dev cycles from the beginning </li></ul><ul><ul><li>Explore the Agile methodology </li></ul></ul><ul><ul><ul><li>For you: More efficient teams (higher collaboration, better product understanding and more view points towards a particular task), you will sleep better at night.  </li></ul></ul></ul><ul><ul><ul><li>For the team: More job satisfaction due to peer to peer type of relationship with their dev counterparts </li></ul></ul></ul>
    21. 21. How to motivate your team cont <ul><li>Consider rotating projects and tasks </li></ul><ul><ul><li>Be also respectful of product attachments within the team… </li></ul></ul><ul><ul><ul><li>For you: Implement best practices (“more eyes” on the project) </li></ul></ul></ul><ul><ul><ul><li>For the team: Challenging, fun and creative environment </li></ul></ul></ul><ul><li>Involve your team members in customer interactions </li></ul><ul><ul><li>If there is an interest within the team… </li></ul></ul><ul><ul><ul><li>For you: More comprehensive test plans and more realistic testing scenarios </li></ul></ul></ul><ul><ul><ul><li>For the team: It’s fun, more empowerment and appreciation because they can contribute more during the development cycle (requirements, test plans, etc) </li></ul></ul></ul> 
    22. 22. Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><li>Marina Gil-Santamaria, Testing Team </li></ul><ul><li>Eric Newcomer, Testing SOA </li></ul><ul><li>Lew Priven, Software Inspections </li></ul><ul><li>Tony Simms, Testing Templates </li></ul><ul><li>Bill Miller, Test Driven Quality </li></ul><ul><li>Patrick Freeman, Software Quality Metrics </li></ul>
    23. 23. Eric Newcomer <ul><li>Meeting New Challenges in Testing SOA </li></ul><ul><ul><li>Flat World Market Trends </li></ul></ul><ul><ul><li>Business Transformation </li></ul></ul><ul><ul><li>IT Transformation </li></ul></ul><ul><ul><li>SOA is the way to achieve transformation </li></ul></ul><ul><ul><li>Testing SOA </li></ul></ul><ul><ul><li>Podrobněji viz dále… </li></ul></ul>
    24. 24. Market Trends <ul><li>Companies have become virtual… </li></ul><ul><li>Blurred lines between company and supplier… </li></ul><ul><li>Outsourcing is location independent </li></ul><ul><li>Key asset is information </li></ul><ul><li>Frequency of change is accelerating! </li></ul><ul><ul><li>Innovation </li></ul></ul><ul><ul><li>Product Cycles </li></ul></ul>
    25. 25. IT Transformation Challenges <ul><li>Applications are built not assembled </li></ul><ul><li>High-cost specialists </li></ul><ul><li>Delivery cycles are costly and often too slow </li></ul><ul><li>Mass Production is needed </li></ul><ul><li>Standardize </li></ul><ul><li>Reuse </li></ul><ul><li>Average developers </li></ul> Revenue Costs New Product Delivery $ Opportunity for business transformation
    26. 26. Move From Monolithic Applications in Steps Intermediate stage: Break out individual services Application Application service service Application Application service Goal: Service-oriented architecture service service service service Application Monolithic applications Application 
    27. 27. Service Contracts Are the Key <ul><li>The key principles of SOA </li></ul><ul><ul><li>Services should be business-oriented </li></ul></ul><ul><ul><li>Services should have well-defined interfaces (aka service contracts) </li></ul></ul><ul><ul><li>Service contracts should separate interface from implementation </li></ul></ul><ul><li>Service contracts are critical to achieving reuse and abstraction </li></ul>
    28. 28. WSDL: Typical Service Contract <ul><li>WSDL is very flexible </li></ul><ul><ul><li>Import existing WSDL contracts </li></ul></ul><ul><ul><li>Create new WSDL contracts using XML Schema </li></ul></ul><ul><ul><li>Create new WSDL contracts from an external metadata source such as CORBA IDL </li></ul></ul><ul><ul><li>Annotate with policy metadata </li></ul></ul><ul><li>Benefits </li></ul><ul><ul><li>Abstraction </li></ul></ul><ul><ul><li>Encapsulation </li></ul></ul><ul><ul><li>Loose-Coupling </li></ul></ul><ul><ul><li>Separation of Concerns </li></ul></ul><ul><li>Logical Contract is what other applications care about </li></ul><ul><li>Physical Contract is extensible to support any middleware binding </li></ul><ul><li>XML Schema provides independent type system </li></ul> Service Port Binding XML Data Type Part Message Operation PortType WSDL Logical Contract Physical Contract
    29. 29. Pre-Certification Process Helps <ul><li>Early Collaboration and Validation </li></ul><ul><ul><li>Extends unit testing to include systems integration level testing </li></ul></ul><ul><ul><li>Moves defects discovered prior to Test deployment </li></ul></ul>Unit Test 1 Unit Test 2 Unit Test 2 Unit Test 1 Advance QA Basic QA Deploy $$ Test Development  Basic QA Basic QA
    30. 30. SOA: Interface Simulation and Testing <ul><li>SOA is based on interface contracts </li></ul><ul><li>Rapid Simulation Solution </li></ul><ul><li>Designed for distributed people/projects </li></ul><ul><ul><li>SOA, Outsourced, Inter-Departmental, B2B, etc. </li></ul></ul><ul><li>Enable parallel development of components </li></ul><ul><li>More efficient use of testing resources </li></ul><ul><li>Enable pre-certification between peer teams </li></ul>Simulate Middleware Web Back-End Simulate Simulate Simulate © 2008 IONA Technologies 
    31. 31. Building a Validation Framework System Test E2E Test Unit Test QA Testing Development Requirements Unit Test Standard Interface Agreements (IAs) Augment current processes to populate and utilize framework Interface Agreement Management System Meta data about code droplets across SDLC Interface Simulator and Testing Validates functional code against design (IAs) Validation Framework System Test
    32. 32. Example: Time to Market Compression PRODUCTION Def Dev Test Backend Billing Systems (eCare/Telegence) Middleware Tier (CSI) Middleware Tier WOW/BAS Tier Def Dev Test Def Dev Test Def Dev Test  Requirements CONSULTATION IONA Framework Def Dev Test IONA Framework Def Dev Test IONA Framework Def Dev Test 7-14 Weeks TTM Improvement
    33. 33. Example: Rapid Website Update <ul><li>.CO.UK business needed high-quality software delivered at “Internet Speed” </li></ul><ul><ul><li>Up to 30 “releases” per year </li></ul></ul><ul><ul><li>Delays are unacceptable </li></ul></ul><ul><ul><li>Only “Priority 1 Defects” can derail releases </li></ul></ul><ul><ul><li>Development teams “must address” P1 defects prior to launch </li></ul></ul>
    34. 34. <ul><li>Reduce Cost of Correcting Defects </li></ul><ul><ul><li>Discovering defects one phase earlier saves $6,600 on average </li></ul></ul><ul><ul><li>Interface framework users have found up to 25 defects per interface: an average of 18 defects </li></ul></ul><ul><li>Reduce Duration of Projects </li></ul><ul><ul><li>Reducing defects in earlier phases allow subsequent phases to complete more rapidly </li></ul></ul><ul><li>Increase Organizational Capacity </li></ul><ul><ul><li>Eliminating defects reduces workloads across the organization </li></ul></ul><ul><ul><li>Resources can be re-invested into improving functionality </li></ul></ul>Some Quantified Benefits Net Results Save $118K per Service Interface Eliminate ten (10) business days per project Increase Overall Capacity 6% 
    35. 35. Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><li>Marina Gil-Santamaria, Testing Team </li></ul><ul><li>Eric Newcomer, Testing SOA </li></ul><ul><li>Lew Priven, Software Inspections </li></ul><ul><li>Tony Simms, Testing Templates </li></ul><ul><li>Bill Miller, Test Driven Quality </li></ul><ul><li>Patrick Freeman, Software Quality Metrics </li></ul>
    36. 36. Lew Priven <ul><li>Software Inspection </li></ul><ul><ul><li>Identifikují chyby ve vývoj software již v době sběru požadavků </li></ul></ul><ul><ul><li>Čím dříve v software life cycle je chyba objevena, tím nižší jsou náklady na její odstranění </li></ul></ul><ul><ul><li>Za 20 let nasbírali zkušenosti a stanovili kde je nejlepší v software life cycle dělat inspekci </li></ul></ul><ul><ul><li>Inspekcí snižují náklady na testování </li></ul></ul>
    37. 37. Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><li>Marina Gil-Santamaria, Testing Team </li></ul><ul><li>Eric Newcomer, Testing SOA </li></ul><ul><li>Lew Priven, Software Inspections </li></ul><ul><li>Tony Simms, Testing Templates </li></ul><ul><li>Bill Miller, Test Driven Quality </li></ul><ul><li>Patrick Freeman, Software Quality Metrics </li></ul>
    38. 38. Tony Simms <ul><li>Tips and Templates for Test Managers, Tony Simms </li></ul><ul><ul><li>Vytvořil a posbíral templates pro podporu testování </li></ul></ul><ul><ul><li>Templates nejsou Brain Transplants </li></ul></ul><ul><ul><li>Pokrytí celého testovacího procesu </li></ul></ul><ul><ul><ul><li>Test Strategy </li></ul></ul></ul><ul><ul><ul><li>Estimating Test Effort & Resource </li></ul></ul></ul><ul><ul><ul><li>Reporting & Tracking Test Milestones </li></ul></ul></ul><ul><ul><ul><li>Daily (weekly) Test Progress Reporting </li></ul></ul></ul><ul><ul><ul><li>End of Testing Report </li></ul></ul></ul><ul><ul><li>Rozdělení zdrojů (40% Requirements, 20% Development, 40% Testing) </li></ul></ul><ul><ul><li>Podrobněji viz dále… </li></ul></ul>
    39. 39. Test Strategy 
    40. 40. Reporting & Tracking Test Milestones 
    41. 41. Reporting & Tracking Test Milestones 
    42. 42. Reporting & Tracking Test Milestones 
    43. 43. Reporting & Tracking Test Milestones 
    44. 44. Reporting & Tracking Test Milestones 
    45. 45. Daily (weekly) Test Progress Reporting Click image above for template <ul><li>Simple, easy to complete daily or weekly report forms make it easy to show project managers the progress and trends in testing. The attached template reports on: </li></ul><ul><li>Test run rate for scripts </li></ul><ul><li>Script pass and fail rates </li></ul><ul><li>% of steps executed </li></ul><ul><li>Issues raised and closed </li></ul>
    46. 46. Tony Simms <ul><li>Anatomy of a Test Strategy, Tony Simms </li></ul><ul><ul><li>Detailně popsal fáze testovacího projektu u uvedl související templates </li></ul></ul><ul><ul><li>Různí stakeholders mají různé požadavky a je třeba je uspokojit všechny </li></ul></ul><ul><ul><ul><li>IT Requirements </li></ul></ul></ul><ul><ul><ul><li>Governance Requirements </li></ul></ul></ul><ul><ul><ul><li>Business Requirements </li></ul></ul></ul><ul><ul><li>Podrobněji viz dále… </li></ul></ul>
    47. 47. Test Phases [template section 6] <ul><li>Detail the relevant Test Phases for the project, a diagram helps visualise the sequence and a phase definition helps all involved ‘speak the same language’ </li></ul> Component Testing Integration Testing System Testing Systems Integration Testing Performance Testing Operations Testing User Acceptance Testing
    48. 48. Work Products This diagram shows which Work Products are to be generated for each phase and activity. Red bordered items are produced once, for the whole project, blue bordered items will be produced for each test phase.  Test Planning Test Preparation Test Execution Test Strategy Master Test Plan Test Environment Requirements Acceptance Criteria High Level Test Specifications Detailed Test Plan Test Data Acceptance Criteria/ Test Spec. Matrix Detailed Test Specifications Test Execution Schedule Environment Utilisation Plan Test Results Report End of Phase Test Reports Incident Reports Test Process
    49. 49. Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><li>Marina Gil-Santamaria, Testing Team </li></ul><ul><li>Eric Newcomer, Testing SOA </li></ul><ul><li>Lew Priven, Software Inspections </li></ul><ul><li>Tony Simms, Testing Templates </li></ul><ul><li>Bill Miller, Test Driven Quality </li></ul><ul><li>Patrick Freeman, Software Quality Metrics </li></ul>
    50. 50. Bill Miller <ul><li>Test Driven Quality </li></ul><ul><ul><li>Vyjmenovává cíle testování </li></ul></ul><ul><ul><li>Ukazuje kdo všechno jsou zákazníci testovacího týmu </li></ul></ul><ul><ul><li>Uvádí kvality dobrého testovacího týmu </li></ul></ul><ul><ul><li>Ukazuje testovací cyklus </li></ul></ul><ul><ul><li>Definuje release criteria a závažnost chyb </li></ul></ul><ul><ul><li>Podrobněji viz příklad dále… </li></ul></ul>
    51. 51. Defect Severity <ul><li>Critical </li></ul><ul><ul><li>Loss of data, instability, and hazardous outcomes.. </li></ul></ul><ul><ul><li>Blocks testing. </li></ul></ul><ul><ul><li>Would harm reputation of company. </li></ul></ul><ul><ul><li>Would harm sales. </li></ul></ul><ul><ul><li>Would lose money. </li></ul></ul><ul><ul><li>Would risk company being liable in a product liability case. </li></ul></ul><ul><ul><li>Would be a danger to people. </li></ul></ul><ul><li>High </li></ul><ul><ul><li>Key features do not work regardless of workaround. </li></ul></ul><ul><ul><li>Leaves the customer with a bad impression. </li></ul></ul><ul><li>Medium </li></ul><ul><ul><li>Minor feature does not work with no work around. </li></ul></ul><ul><ul><li>A visual error. </li></ul></ul><ul><li>Low </li></ul><ul><ul><li>Minor feature does not work, but there is a work around. </li></ul></ul>
    52. 52. Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><li>Marina Gil-Santamaria, Testing Team </li></ul><ul><li>Eric Newcomer, Testing SOA </li></ul><ul><li>Lew Priven, Software Inspections </li></ul><ul><li>Tony Simms, Testing Templates </li></ul><ul><li>Bill Miller, Test Driven Quality </li></ul><ul><li>Patrick Freeman, Software Quality Metrics </li></ul>
    53. 53. Patrick Freeman <ul><li>Software Quality Metrics for Critical Decision Making </li></ul><ul><ul><li>Uvádí sedm Software Quality Metrics a typické počty chyb pro každou metriku </li></ul></ul><ul><ul><li>Uvádí seznam metrik, na základě kterých nedoporučuje rozhodovat </li></ul></ul><ul><ul><li>Jako Capture Deffect Tool doporučuje Quality Center, Excel nebo Bugzilla (zejména tu doporučuje) </li></ul></ul>
    54. 54. Nejzajímavější přednášky <ul><li>Luis Carlos da Silva, Case Study </li></ul><ul><li>Greg Stone, Case Study </li></ul><ul><li>Marina Gil-Santamaria, Testing Team </li></ul><ul><li>Eric Newcomer, Testing SOA </li></ul><ul><li>Lew Priven, Software Inspections </li></ul><ul><li>Tony Simms, Testing Templates </li></ul><ul><li>Bill Miller, Test Driven Quality </li></ul><ul><li>Patrick Freeman, Software Quality Metrics </li></ul>
    55. 55. Shrnutí Headlines PSQT 2008 <ul><li>Testing Team Motivations by Marina Gil-Santamaria </li></ul><ul><li>Software Inspections by Lew Priven </li></ul><ul><li>Testing SOA by Eric Newcomer </li></ul><ul><li>Testing Templates by Tony Simms </li></ul>
    56. 56. Poučení z PSQT 2008 <ul><li>Testovací tým </li></ul><ul><ul><li>Vylepšit atmosféru, prostředí - odbourání stresu, vyšší výkon </li></ul></ul><ul><ul><li>Důležité, aby testeři věděli, co testují, jaké je použití, znali historii produktu, mohou pak nejen testovat, ale i test připravovat </li></ul></ul><ul><ul><li>Regresní testy dělat až v okamžiku, kdy je aplikace stabilní </li></ul></ul><ul><ul><li>Zaznamenávat výsledky testů a prezentovat je testerům pro zvýšení motivace </li></ul></ul>
    57. 57. Poučení z PSQT 2008 <ul><li>Vztah TEST a TECH týmů </li></ul><ul><ul><li>Nutno popsat SLA mezi TECH a TEST </li></ul></ul><ul><ul><li>Zaznamenávat výsledky testů a reportovat je TECH </li></ul></ul><ul><ul><li>Reportovat podíl chyb ve skupinách </li></ul></ul><ul><ul><li>Všechny chyby reportovat konsistentním způsobem </li></ul></ul><ul><ul><li>Zavlečené chyby re-open a reportovat TECH </li></ul></ul><ul><ul><li>Určit zodpovědnost za provádění integračního testu </li></ul></ul><ul><ul><li>Zástupce TECH v TEST týmu při plánování </li></ul></ul><ul><ul><li>Zapojení businessu do testování (alespoň na konci UAT) </li></ul></ul><ul><li>pro TECH zavlečené chyby </li></ul><ul><li>pro správu testovacího prostředí chyby prostředí </li></ul><ul><li>pro navazující systémy chyby v navazujících systémech </li></ul><ul><li>pro TEST tým chyby testů </li></ul><ul><li>pro BUS tým chyby vzniklé z nepochopení dokumentace </li></ul>
    58. 58. Poučení z PSQT 2008 <ul><li>Automatizace testů </li></ul><ul><ul><li>Vhodná pouze u regresního testu </li></ul></ul><ul><ul><li>Vhodná pouze je-li aplikace stabilní </li></ul></ul><ul><ul><li>Vhodná pouze jsou-li testovací data stabilní </li></ul></ul><ul><ul><li>Nepodařilo se najít srovnatelnou formu pro posouzení vhodnosti automatizace </li></ul></ul>
    59. 59. Podrobněji o PSQT 2008 <ul><li>Popis nejzajímavějších přednášek v souboru PSQT 2008.doc (6 stran) </li></ul><ul><li>Podrobné materiály k celé konferenci v souboru Welcome.jpg (1021 stran) </li></ul><ul><li>Na emailu: [email_address] </li></ul><ul><ul><li>Odpovědi na další otázky </li></ul></ul><ul><ul><li>Pomoc při kontaktování přednášejících </li></ul></ul><ul><ul><li>Uspořádání seminářů nebo konzultací s Tony Simms </li></ul></ul><ul><ul><li>Uspořádání konzultací s Lew Priven </li></ul></ul>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×