Independent testing « Softheme Blog » Software Outsourcing Ukraine

Posts Tagged ‘Independent testing’

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:

(more…)

Bookmark/Search this post with:

Aggiungi 'Softheme Approach to Testing Web Projects' a Del.icio.us

Aggiungi 'Softheme Approach to Testing Web Projects' a digg

Aggiungi 'Softheme Approach to Testing Web Projects' a reddit

Aggiungi 'Softheme Approach to Testing Web Projects' a Technorati

Aggiungi 'Softheme Approach to Testing Web Projects' a Stumble Upon

Aggiungi 'Softheme Approach to Testing Web Projects' a Social Bookmarking Reloaded

Tags: approach to testing, bug tracking, defects tracking, Independent testing, Software testing, test case, test plan, test strategy, testing, testing approach, web projects
Posted in Independent testing, Quality assurance, Software testing | 1 Comment »

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…)

Bookmark/Search this post with:

Aggiungi 'Softheme Test Specialists' a Del.icio.us

Aggiungi 'Softheme Test Specialists' a digg

Aggiungi 'Softheme Test Specialists' a reddit

Aggiungi 'Softheme Test Specialists' a Technorati

Aggiungi 'Softheme Test Specialists' a Stumble Upon

Aggiungi 'Softheme Test Specialists' a Social Bookmarking Reloaded

Tags: business logic, Independent testing, non-functional testing, regression testing, Software testing, test cases, testing approach, testing specialists, top managers
Posted in Independent testing, Quality assurance, Software testing | No Comments »

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…)

Bookmark/Search this post with:

Aggiungi 'Testing Approach: Incident Management' a Del.icio.us

Aggiungi 'Testing Approach: Incident Management' a digg

Aggiungi 'Testing Approach: Incident Management' a reddit

Aggiungi 'Testing Approach: Incident Management' a Technorati

Aggiungi 'Testing Approach: Incident Management' a Stumble Upon

Aggiungi 'Testing Approach: Incident Management' a Social Bookmarking Reloaded

Tags: incident management, incident report, Independent testing, Software testing, testing approach
Posted in Application development, Custom application development, Independent testing, Quality assurance, Software testing | 4 Comments »

Controlling the Test Progress

Tuesday, May 12th, 2009

One of the most important parts of testing management is controlling the test progress. The purpose of test progress monitoring is to provide feedback and visibility of the progress of test activities. The test metrics are used to track progress towards the completion of testing, which is determined by the exit criteria. Test metrics include:

Percentage of test cases prepared
Environment readiness
Test case execution
Defect information (density, amount of fixed/not fixed, failure rate, retest results)
Test coverage of requirements
Subjective confidence of testers in the product
Dates of test milestones
Testing costs

(more…)

Bookmark/Search this post with:

Aggiungi 'Controlling the Test Progress' a Del.icio.us

Aggiungi 'Controlling the Test Progress' a digg

Aggiungi 'Controlling the Test Progress' a reddit

Aggiungi 'Controlling the Test Progress' a Technorati

Aggiungi 'Controlling the Test Progress' a Stumble Upon

Aggiungi 'Controlling the Test Progress' a Social Bookmarking Reloaded

Tags: exit criteria, Independent testing, monitoring, Software testing, test activities, test metrics, test progress, test report, test strategy, test summary report
Posted in Independent testing, Quality assurance, Software testing | No Comments »

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