| Home : Testing : Test Approach |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
Test Approach Listings
|
|
Total:
17 | Displaying: 1 - 10 | Pages: 1 2 >> |
|
|
|
Automating ADC Data Collection.This article describes an automated data collection system for analog-to-digital converters (ADCs). It discusses the advantages of automating data collection as well
as a detailed description of the hardware and software. It goes on to explain the
operation of the system and give some data examples.
Updated: 05/31/2005
|
|
|
Although developers have been unit testing their code for years, it was typically performed after the code was designed and written. As a great number of developers can attest, writing tests after the fact is difficult to do and often gets omitted when time runs out. Test-driven development (TDD) attempts to resolve this problem and produce higher quality, well-tested code by putting the cart before the horse and writing the tests before we write the code. One of the core practices of Extreme Programming (XP), TDD is acquiring a strong following in the Java community, but very little has been written about doing it in .NET.
Updated: 05/21/2005
|
|
|
The Unified Modeling Language Testing Framework
Updated: 04/17/2005
|
|
|
Testing applications on Pocket PCs requires a special strategy and plan. It’s different from testing normal client/server or Web-based application. Testing applications for Pocket PCs is like a mixture of strategies applied for testing client/server and Web-based applications.
Updated: 04/17/2005
|
|
|
theory of fault-based program testing is defined and explained. Testing is fault-based when it seeks to demonstrate that prescribed faults are not in a program. It is assumed that a program can only be incorrect in a limited fashion specified by associating alternate expressions with program expressions. Classes of alternate expressions can be infinite. Substituting an alternate expression for a program expression yields an alternate program that is potentially correct.
Updated: 04/17/2005
|
|
|
The purpose of this paper is to describe general data warehouse structure and background, as well as specific situations encountered during the testing effort for our project. Our project was to test a data warehouse and data mart for a large research department of a pharmaceutical manufacturing company. This was a pilot project and our efforts, if successful, would pave the way for future data warehouse projects within the company. Our role on the project team was to provide quality through validation of the business rules. We met this challenge by determining if the extract/transform/load (ETL) process was functioning in the approved manner. We created basic principles that were used as a starting block for our process.
Updated: 04/17/2005
|
|
|
Test Automation Snake Oil
Updated: 04/17/2005
|
|
|
I've used lots of methods to transform data between databases and object code. From hand-coded SQL to JDO to EJB. I've never found a method I liked particularly well. This distaste has become especially acute since adopting test-driven development (TDD) as a guiding philosophy.
Unit-testing should have as few barriers as possible. For relational databases those barriers range from external dependencies (is the database running?) to speed to keeping the relational schema synchronized with your object model. For these reasons it is vital to keep database access code away from the core object model and to test as much as possible without touching a real database.
Updated: 04/13/2005
|
|
|
Organisational Approaches for Testing
This paper describes three organisational approaches for unit testing: top down, bottom
up and isolation. The organisational approach is a key element of unit test strategy and
planning; selection of an inappropriate approach can have a significant impact on the
cost of unit testing and software maintenance. A unit test strategy based on isolation
testing is recommended.
Updated: 04/06/2005
|
|
|
This document has been created as a guide to help testing professionals select, understand and implement functional test tools in their organisation.
Due to the large number of test automation tools available I have followed the 80/20 rule and selected the most popular as a base for this document. However where necessary other products including, Test Management, performance test and defect tracking suites will be mentioned.
This base includes the following: Rational Robot (as included in Rational TestStudio) 2001,Rational Visual Test 6.5,Mercury WinRunner 7,Segue SilkTest 5.?,Compuware QA Run 4.7.?(as included in QACenter)
Updated: 04/05/2005
|
|
|
Test Approach Listings
|
|
Total:
17 | Displaying: 1 - 10 | Pages: 1 2 >> |
|
|
