Posts Tagged ‘exit criteria’

How We Assist in Your Product’s Improvement

Wednesday, May 27th, 2009

It is a matter of fact that bugs cost a lot of money to companies developing different kinds of software products. We at Softheme help these businesses to save their budgets spent on bugs fixing. By virtue of our independent testing service, we assist companies in their product scalability and performance improvement.

Softheme is characterized by providing a flexible, adaptable, speedy, simple and yet thorough approach to testing. Maintaining a partnership spirit with our customers, we develop a roadmap in achieving well-defined goals in regards to test standardization, application quality, business risk, project cost, and time-to-market.

By providing independent testing service, i.e. carrying out testing of the code that has been created by another vendor, Softheme makes it possible to improve the effectiveness of software testing as well as incorporate all testing elements into a comprehensive and dedicated quality assurance program.

The key benefits of independent testing are:

  • The tester can see what has been built rather than the developer thought has been built;
  • The tester makes no assumptions regarding quality;
  • The tester is unbiased.

(more…)

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

SWIT Investor Day