Quality assurance Presentation

  • Notre présentation --> 31 mars

  • L'industrie a été très lente a devenir plus attentif au quality assurance.
  • Un domaine essentiel si on veut réussir… C'est évident… wink
  • Process
    • Extreme programming
      • You have to work hand in hand with the customers.
      • Write test first with real data with the customer.
    • RUP
      • Weak on testing
      • An iteration is something that can be tested
    • ISO
      • Aucun vendeur n'est ISO car le process est trop compliqué.
    • Carnegie Mellon Univ.
      • La meilleure université au monde pour SEG…
      • Capability Maturity Model
        • Comment ton process de quality est mature
        • Level 1 to 5
        • On a vu ça en test..
  • Productivity
    • Quality insurance increase productivity…
    • Nightly builds with simple tests increase productivity too because you notice the next day that the code is broken…
    • Quality assurance is not only testing
    • On fait du testing dans chacune de phases du projet.
    • Quand fait-on notre testing?
    • Chaque programmeur travaillant sur un bout de code est responsable de son code mais du test pour ce code aussi. Donc dans un nightly build pour réussir, les tests doivent fonctionner aussi.
  • QA presentation
    • What level of quality is requiered for our project?
      • e-commerce: quality high
      • New technology (research): quality low
    • How far should we go on quality
    • What are the 2-3 things the most important for our testing process… What should we do first?
    • 15 min + 5 min de questions
    • Il peut poser des questions en plein millieu, il tiendra compte du fait que ça vole du temps de notre présentation.
    • Se fixer un point qu'on voudrait que tout le monde se rappel le lendemain. Structurer notre présentation en fonction de ça!
    • Focuser sur les 3 choses les plus importantes.
    • Pas plus de 7 choses sur une même slide (même screen).
    • Une bonne slide = titre + 3 sous titres explicatifs
    • Ne pas oublier de bien présenter le projet et tous nos objectifs
    • What is our strategy?
      • Code inspection?
      • Architecture inspection?
      • Unit testing?
    • Explain how the strategy is going to work and relate it to how it'll help to meet the requierements.
    • Show 1 or 2 tests cases
      • Take 1 critical scenario and show what is the testing for this.
      • Someone else who dont know the project can repeat the test and get the sam results.
    • How the QA manager is going to communicate the results.
      • What is the state of the system?
      • How close are we to meet all the requirements.
        • Define test for all the requirements and 70% are passing right now for example.
      • Group tests in groups
        • Security test
        • Performance test
        • GUI test
    • Breif test plans
      • Major milestones for wich tests we need to build in wich milestone etc…
    • We need to have ONE thing everybody will remember the next day… Seems important to him ;).
    • Automated GUI testing
    • Wait until near the end of the project… Since the GUI will change a lot.
    • Acceptance Testing/Usability Testing
    • The real users are trying the program
      • Target the right user
      • How many task do they do right
      • How many task they took too much time…
      • Tape it and analyse it later
    • No one on the project team can do this… We need real users.
    • How do we define usability?
    • Non functionnal testing
    • Testing non-functionnal requierements
      • Try to find a way to qualify it
    • Ex: easy to maintain
      • Code inspection
        • Verify in such a way that it should be easy to maintain
        • We agreed on a way to code that should be easy to maintain
    • Subclass the non-functionnal requierements into smaller requierements
  • Security
    • Is really important on the internet
    • Minimize security risks
  • Robustness
    • How long can your system run before it crash
    • A server should never crash!
      • Try/catch at the highest level
      • The only way the server could crash is running out of ressources
    • Try to make the server work 24h/24 and try to see when it'll crash
  • Scalability
    • How much volume can your web site can handle.
      • Simultenious requests for example.
      • What is the peak situation
      • Have simulations that cause peak time to test it.
    • Setup for the example the web site so that we can run the software on 5 machines at the same time… (Cluster)
  • The main focus for this iteration is not the presentation. It`s building the process of ensuring the delivery of the system. Let's have a demo able to run some critical scenarios…
  • So you can have feedback from the customer.
  • In iteration 4 you can reengineer and rewrite the code to be really nice and SEGalike...

-- EtienneTremblay - 07 Mar 2005
Topic revision: r1 - 07 Mar 2005, EtienneTremblay
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback