Posts Tagged ‘test strategy’

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:

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

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

Softheme Software Testing Approach

Tuesday, May 5th, 2009

Today we believe is the high time to open a new discussion section in this blog and share some of our experience regarding independent testing services we have been providing since the inception of Softheme. From the very start of our company we have built a strong QA department with the aim to help our customers bring only high-quality products to the market. Now we can be proud of how this departments develops and the results we keep delivering to our clients.

In the next several posts we would like to offer such information as the description of our testing approach, testing case studies, and samples of testing documentation for your review; and hope that you will find this information interesting and helpful for your business or personal use.

(more…)

SWIT Investor Day