Fundamental Test Process

Basics for test process in everyday bases. Ideal to give you a higher level ideal of what a software tester do.

Ideal for a Junior Software Tester or who is intend to take the ISTQB-ISEB exam.

Download the High-Resolution image. (PNG format)

Download the A3 size to print in that size. (PDF format)

Fundamental Test Process
Fundamental Test Process – Click to Enlarge

Download the High-Resolution image. (PNG format)

Download the A3 size to print in that size. (PDF format)

I have shared this mind map so you can copy and amend if you want to.

Create your own mind maps at MindMeister

Download the Mindmeister file. (.mind format – Zip file)


If you don’t have a MindMeiter Mind Map account, register for free here – http://www.mindmeister.com/?r=177956

Fundamental Test Process
1. Planning & Control Planning

  • Determine the scope, risks & objectives
  • Implement Test Policy / Strategy
  • Determine Test Approach
  • Determine resources required
  • Schedule the test activities
  • Determine the Exit Criteria

Control

  • Monitor activities
  • Compare progress vs plan
  • Take control when required

2. Analysis & Design

  • Review the Test Basis
  • Eval Test Basis for test-ability
  • Identify & priorities Test Conditions
  • Design & priorities high level Test Cases
  • Identify Test Data
  • Trace-ability between Test Bases & Test Condition
  • Test environment & Infrastructure tools

3. Implementation & Execution Test Implementation

  • Finalise, Implement & prioritise Test Cases
  • Create Test Data
  • Check environment ready
  • Create Test Suites
  • Develop & priorities Test Procedures
  • Test harness / automated scripts (optional)

Test Execution

  • Execute Test Procedure as planned
  • Log the outcome
  • Compare actual vs expected
  • Report discrepancies as Incidents
  • Analyse Incidents for cause
  • Retest / Regression

4. Evaluating Exit Criteria & Reporting

  • Check logs against Exit Criteria
  • Assess if more test are needed or Exit Criteria need to be changed
  • Write Test Summary Report for stakeholders

5. Test Closure

  • Check planned deliverables
  • Close Incident Reports
  • Handover to maintenance
  • Finalise & archive test-ware / environment
  • Document acceptance of system
  • Analyse lessons learned for future projects & improve test maturity

Tools I’ve used to help with the video and mind mapping:

Mind MappingMindmeister – Plan and brainstorm online with friends with the free mind mapping tool MindMeister http://www.mindmeister.com/?r=177956

Resources:

http://en.wikipedia.org/wiki/Software_test_documentation

Click to access ieee829mtp.pdf

http://standards.ieee.org/findstds/standard/829-2008.html

Click to access SQETestIncidentReportTemplate.pdf

http://www.geekinterview.com/question_details/46503

Sending
User Review
5 (1 vote)

Rogerio da Silva

Business & Test Analyst | Website Consulting | Email Consulting | Microsoft Dynamics 365 CRM QA | Agile | Manual | Integration & Automation | DevOps | API | Cloud | AI | IoT | CRM | Looking for Scalable Services? InShore, OffShore or Hybrid
Interested? Ask me how we can help.

%d bloggers like this: