Below is the detail that should be included in a standard test plan. Introduction Purpose of Document The purpose of this document is to record the agreed Test Plan to be adopted during the ?????  testing of the ????? Project. This document identifies the approach, schedule, Items and requirements / pre-requisites for the testing to Read More →

Defects Over the years i have found that different areas of organisations have very different interpretations of defect priority and severity, the levels and even use the terms interchangeably, this post should hopefully clear up the difference between the terms with reference to defects. Severity Severity is the measure of impact upon the ‘Quality Characteristics’ Read More →

Ingredients Serves: 4 600 ml (1 pint) semi-skimmed milk 1 onion or 2 shallots, halved 1 bay leaf 6 black peppercorns pinch of grated nutmeg 55 g (2 oz) butter 55 g (2 oz) plain flour salt and pepper Method Prep:15min  ›  Cook:5min  ›  Ready in:20min Pour the milk into a heavy-based saucepan and add the Read More →

I completed an evaluation of the Zephyr Enterprise Test Management tool (integrated with Jira) using HP QC as a baseline, the below findings from the evaluation pull out the key issues and are broken down into Advantages (This is something new), Neutral (This is something QC does or it is new but a bit cumbersome) Read More →

I have recently put together a Test Approach for an Agile project, below is the document structure I used, this is not a formal test plan as the detail required to create a test plan was not available. The document I created was designed to give an idea of the testing activities in an Agile Read More →

I have a question, why is it called User Acceptance Testing? Users / Product owners should be part of the development process to validate requirements and what is being built, Testers should test the system to an appropriate level of coverage. By the time it gets to the Users prior to sign off they should Read More →