Software testing


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Software testing

  1. 1. Quality in application developmentOrganisations are becoming increasingly aware ofthe importance of quality at all levels.This trend is now also making itself felt inapplication development. Businesses areconstantly setting higher standards as far as thequality and usability of their applications areconcerned, as well as for output reliability. That iswhy software testing is now a vital component ofquality and risk management. SWTEST180210ENG Ordina Belgium • Blarenberglaan 3B • B-2800 Mechelen • Belgium  +32 (0)15 29 58 58
  2. 2. Software testing, faster and betterSoftware testing, faster and better Based on the V-modelWhy software testing? Quality in the entire development cycleBy testing software defects can be identified. You can then Ordina has developed a structured approach to softwareremove them before going into production. This prevents testing. This is based on the V-model for softwaredefects to affect the integrity and the correct processing development. This creates a correlation between theof your data, and as a result the quality of your services various phases of development and testing. Each phaseand products. By professionally documenting the starts on the basis of detailed documentation of theoperation of the system, you also demonstrate that the previous phase. This approach guarantees qualitysystem operates in accordance with the specifications. throughout the entire life cycle of a development project.Software testing with OrdinaOrdina has developed a structured approach to testingwith considerable attention being paid to riskmanagement. Ordina learned the tricks of the trade in thestrictly regulated pharmaceutical sector. By adopting arisk-based approach Ordina focuses on the critical pointsin a development process without jeopardising the qualityor the safety of the software. For certain types of testassignments Ordina collaborates with the social profitcompany Passwerk. Testing at various levels Software can be tested at various levels: 1. Component testing: do the components that have been developed operate as stipulated in the design? 2. Integration testing: do the components do what they are expected to do when you interconnect them? 3. System testing: does the system operate as a whole: is it performant, can it manage large volumes, can it handle peak loads, is the documentation usable, is the system stable and reliable in all circumstances?Testing tools 4. Acceptance testing: does the system do what theOrdina prefers to use testing tools in order to verify the client expects it to do?quality of applications. Every Ordina tester has experience Test strategywith HP Quality Center and other tools. Test tools are used Do you need to test your software at every level of theto create test scenarios, analyze test results, trace test development cycle for each individual project? Notactivities and automate the execution. If no tools are necessarily. Ordina determines your test strategy on theavailable, Ordina may either use templates to track the basis of questions, such as:process or employ a testing management tool that wasdeveloped in-house. how complex are the system and its components? how familiar is the development team with the processes, development methods and tools? how critical is the process to be automated to your company’s operation? in which parts of the development process can one expect potential risks? 2More info? Please call Bart Van Acker +32 (0)15 29 58
  3. 3. Software testing, faster and betterRisk-based approach Advantages of a risk-based approach By adopting a risk-based approach you map out the criticalFocus on critical aspects risk factors, and you will obtain a clearer picture of theOrdina takes a risk-based approach to testing. Its basic scope for the test activities. The approach clarifies whichprinciple: spend your valuable time and energy on those records, system activities and application processes youcomponents which present the greatest risk, without have to monitor when setting up an audit trail. Finally, ajeopardising the quality or safety of the software. This is risk-based approach can form the basis for monitoring thelogical, because critical components require more testing integrity and reliability of your records throughout theirthan those that are less critical. If you perform a risk entire life cycle.analysis at the right stages of a project, then you will saveconsiderable amounts of money at the testing stage and Justify the approachwhen executing the code. Scale up or down the requiredRisk analysis effortThe risk analysis focuses on: Focus on critical functions of your process the possible impact of an error; the probability of an error occurring; Support successful process & system development the chance of an error being detected when it Support maintenance of the occurs. qualified state, the change management processThe most suitable approach With a risk analysis you will achieve several objectives.Based on experience and best practice, Ordina opts for themost suitable approach for your new developmentproject– such as Failure Mode and Effects Analysis (FMEA),Ishikawa diagrams, Fault or Event Tree Analysis, or Hazard Risk-based approach with OrdinaAnalysis Critical Control Point (HACCP). Implementation: An experienced quality consultant Scenario: The quality consultant performs the risk analysis and documents the findings. The analysis takes two days per business process – one for the implementation and one for the documentation. Participation of key users or business process owners is crucial. References: e.g. Alcon, Institute for Tropical Medicine, Johnson & Johnson, Pfizer, Qualiphar, Red Cross, etc. 3More info? Please call Bart Van Acker +32 (0)15 29 58
  4. 4. Software testing, faster and betterTest management Testing software with PasswerkWorking with a test manager Autistic people as test engineersThe larger the project, the larger the test team. For large In 2008, Ordina Belgium participatedor more complex projects it is wise to appoint a test in setting up Passwerk: anmanager, whose main duties will be: organisation that focuses on co-ordination: follow-up of test engineers, planning, software testing carried out by project progress, etc.; normally gifted people with an first point of contact for the designers with questions autism spectrum disorder. Autistic people work about defects, and for the management concerning accurately, thoroughly, efficiently, and they are focused. e.g. the status of the test project; Furthermore, they love repetitive tasks and long-term assignments. This makes them excellent test engineers. if required, reporting on the progress of the software quality and project status, for example. Setting the bar highOn larger projects it is recommended to support the test Passwerk sets the bar very high in matters of recruitment,manager with specific tools. training and guidance of its test engineers. The tests are co-ordinated by experienced professionals at Ordina or byWorking with test scenarios the client. Ordina also monitors the quality of the workA structured approach to testing requires that the possible supplied. This ensures optimum results. Passwerkscenarios are documented in test cases. For test scenarios combines business challenges with a social dimension.Ordina works on the basis of the following principles: Working with Passwerk underlines your socially prepare test cases based on the business and user responsible entrepreneurship. requirements, functional and technical specifications; only then will the final result meet the expectations of the users; In a nutshell: save the test scenarios after delivery of the project; software testing with Ordina they can often still prove highly useful for upgrades and maintenance of the application. Implementation: Passwerk (test engineers) and Ordina (test engineers, test co-ordinators and test managers)Reporting bugsOrdina test engineers pay considerable attention to clear Three scenarios:reporting about the defects detected. Thus, the 1. Ordina co-ordinates and manages the test process.developers can quickly and accurately reproduce and solve The test co-ordinator writes the test plan. The clientthe errors. Using the script as the basis, the test engineer prepares the test scripts and carries them out. A testwill check whether the error has effectively been solved. If co-ordinator or test manager will be appointed onnecessary, he will also perform regression tests. These larger and more complex projects.check whether the corrections made have not led to any 2. An Ordina test co-ordinator prepares the test errors occurring in the programmes. The client carries them out. 3. Ordina is responsible for the entire test process. References: e.g. Acerta, Agfa, Digipolis, Fortis, KBC, Mobistar, Proximus, Telenet, VDAB, Wolters-Kluwer.Ordina branches in Belgium and LuxembourgBlarenberglaan 3B, B-2800 Mechelen, Tel. +32 (0)15 29 58 58 Route d’Arlon 94; L-8311 Capellen, Tel. +352 26 30 33-25Gouv. Roppesingel 25, B-3500 Hasselt, Tel. +32 (0)11 30 38 38 4More info? Please call Bart Van Acker +32 (0)15 29 58