Short Description ...

Any form of internal tests (before acceptance by the customer) and acceptance-tests (clients and contractors together or just the client). 

Our SERVICES ... 

• Test planning and test specification:
  - Development and definition of useful test cases
  - Specification and preparation of test data
  - Selection and supply of test tools
  - Time and resource planning (in accordance with the project management)
• Test execution:
  - external execution of all necessary test cases
  - Supplying ISTQB certified testers for your tests
  - Managing test execution and internal test teams (by our consultants with certified tester certification)
• Test logging and test analysis:
  - Development of a test log for all executed tests
  - Development of a summarizing list of defects
  - On demand we give objective and critical comments with recommendations for future strategies ...  
• Module tests:
  - directed inspection of single system components
  - boundary value analysis
  - tests with different volumes of data (performance tests)
  - dummy tests (‚fool-proof’?)
  - crash tests (robustness, integrity, ..)
  - ...
• Integration tests:
  - analysis of embedding into other system modules, components
  - Interface tests (syntax and semantics)
  - testing/simulation of complete use cases before acceptance tests
• Web-/browser tests:
  - special test for web applications
  - different browsers
  - different internet and system settings
  - testing security relevant components and settings
  - other factors (cache performance, screen resolution, fonts, ...)
• Coaching for preparation and execution of acceptance tests:
  - talks and workshops with project managers, product developers and/or clients
  - cooperative definition of the approach and framework for the acceptance test
  - assistance on demand while acceptance test is going on
• Execution of acceptance tests/validation:
  - internal acceptances of specifications, requirement specifications and intermediate results
  - methodical checks on relevant criteria (see detailed description below) and contractual agreements
  - Development of an acceptance log with found defects and recommendations for future strategy
• ...

Customer quotes ...

Project: "Testprozessanalyse und -optimierung" at BMD Systemhaus GmbH, März 2003:

(BMD is one of the largest software companies in Austria and leader in the area of accounting software in Austria)

 "For more than 12,000 BMD customers, who - forced by law - have to obtain up to four updates a year, SW quality assurance isn't a side issue, but a vital one!

Software Quality Lab has been supporting us to optimize the test process and above all stressing its importance!"

Quote: BMD Systemhaus.

We will be happy to provide you the contact data for this reference on request. 

Further infos about this area of services ...

Programming mistakes are difficult to avoid.

Reasons are often project time pressure, no applicable knowledge on systematical test execution, not enough experience or user-view understanding by the developers, ambigous specifications, mistakes in used development tools, ...

In this field we can take over the internal test execution for our clients, partially or entirely, acting as an external test lab.

Systematic testing finds much more defects than usual developer testing and enables the achievement of prefefined product quality standards.

Systematic testing covers detailled test planning and test specification, methodical test execution, test logging and analysis.

You can find additional information in our Newsletter on software testing.

Some special comments for software acceptance ...

Acceptance testing of software is related to all moments in software development and maintenance where intermediate or end results are given and processed by groups of employees or other contractors.

In this process the intermediate/end results are compared to agreements.

The acceptance of a specification between contractor and client or between specification developer and future system users can happen on completion of the specification itself, when the implementation is outsourced to an external service provider and of course when the implemented result is delivered from the external service provider to the customer.

It may also prove useful to perform the acceptance tests by other occasions - e.g. important milestones, in order to determine the future course of the project.

Through acceptance tests it is guaranteed that given intermediate or end results will fit the user requirements.

Acceptance covers the following aspects, e.g.:

- is the level of details good enough? 

- check of completeness of figures and statements

- is the content correct from the view of future users?

- Testing of usability from the view of the future end user 

- does the system match the requirements of perfomance?

- Analysis of security issues