Posts Tagged ‘testing approach’

Software Testing: History, Trends, Perspectives - a Brief Overview

Friday, September 3rd, 2010

In this presentation below we have tried to describe software testing process, different types of testing, the prospects of testing in near future, explain some methodologies.

Softheme Approach to Testing Web Projects

Wednesday, May 20th, 2009

Softheme approach to testing web projects contains the following steps:

1. Analyze project business requirements and functional specifications that will be used as a reference and basis;
2. Get familiar with the application that is planned to be tested (if available);
3. Create Vision document that describes approach to testing, identifies project schedule, tools, deliverables, team profile;
4. Estimate Level of Efforts, come up with costs;
5. Approve Vision and LOE;
6. Identify testing approach:

Softheme Test Specialists

Monday, May 18th, 2009

We thought that when discussing our testing approach it would be unfair if we said nothing about the test specialists at Softheme without whom our success in software testing services would be impossible.

Our test specialists are comprehensively trained as their level should correspond to a level of complexity of the projects tested. At Softheme we implement a training period (11 – 12 months) during which a test specialist studies approaches and standards required to properly and effectively test projects.

During the first three months a test specialist tests modules which functionality is intuitively clear using existing sets of test cases. On this stage a test specialist learns formats of Test Cases and how to report defects.

After that, during the following three months, a test specialist starts creating Test Cases for UI and easy to understand sections of business logic.

(more…)

Testing Approach: Incident Management

Thursday, May 14th, 2009

Restoring a normal service operation and minimizing impact on business operations is the work of incident management. The process of incident management ensures that incidents (actual result is different from the expected result) are tracked. The task of test engineers involved in the project is to record and classify the incidents for further investigation.

Incidents are raised on incident reports which have the following objectives:

  • To provide developers feedback on the problem to enable identification, isolation and correction as necessary.
  • To provide test leader with a means of tracking the quality of the system under test and the progress of testing (number of incidents, their status).
  • To provide ideas for test process improvement.

(more…)

Testing Approach: Continued

Thursday, May 7th, 2009

In this post we will continue discussing our software testing approach. Today we would like to say a few words about how we approach test strategy and test planning.

1. Defining Test Strategy

A test approach or test strategy defines how testing will be implemented. There are many approaches that can be employed as is or combined if required:

  • Risk-based testing: test areas with greater risk
  • Model-based testing: test the areas that are used most
  • Method-based testing: test most possible errors, user checklists and quality characteristics
  • Standards-based testing: test application against the industry listed standards
  • Dynamic testing: testing with concurrent execution and evaluation of the results
  • Domain-driven testing: test using domain-specific methodology
  • Regression-averse testing: test using existing templates

(more…)

SWIT Investor Day