| Home : Testing : Test Process |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
Test Process Listings
|
|
Total:
44 | Displaying: 1 - 10 | Pages: 1 2 3 4 5 >> |
|
|
|
ANTS™ is a suite of products dedicated to optimizing and analyzing the performance of .NET applications. Choose one of the products below to read the basic facts.
Updated: 05/21/2005
|
|
|
Learn about the unit testing features of Team Test from a TDD, test-then-code approach with this walkthrough. This article explains how to create Team Test unit tests. We begin by writing a sample assembly, and then generating the unit test method stubs within that assembly. This will provide readers new to Team Test and unit testing with the basic syntax and code. It also provides a good introduction on how to quickly set up the test project structure. Next, we switch to using a test driven development (TDD) approach in which we write unit tests before writing the production code.
Updated: 04/23/2005
|
|
|
Testing use cases requires understanding the concept of UML and use cases. This article aims at introducing the user to UML and use cases (one of the nine diagrams) and how to derive test cases and test scenarios from use cases.
Updated: 04/17/2005
|
|
|
This is full book 11 chapters. The main purpose of the book is to provide a bridge across the gap between the theoretical research and the practice in software testing. The target readers of the book are, therefore, two groups. From the practical side come the software engineers who have some experience in software testing, and students of computer science who have taken courses in software engineering and have some knowledge of software verification and validation techniques, especially software testing techniques. The book surveys various approaches to adequate testing of software and attempts to put them into a uniform framework so that software engineers can understand. The book will help software engineers to understand the foundation of their work and the ways to improve their performance.
Updated: 04/17/2005
|
|
|
Monitoring the performance of distributed systems remains one of the great challenges for IT managers today -- one that has only intensified with the advent of Web services. According to Diane Hagglund, director of product marketing at Freshwater Software, the evolution of enterprise systems away from the client/server model to the highly distributed systems typical of Web services infrastructures is causing a shift in monitoring paradigms to support the underlying architecture.
Updated: 04/07/2005
|
|
|
Team building sessions: few like to attend those things. Yet, the benefits of teamwork are constantly praised and rewarded. Even this article praises teamwork, but does not suggest any touchy-feely exercises to bring test and development teammates closer together. Deborah Kablotsky specifically covers understanding each other and working together throughout a project's lifecycle, a proven way of working together to shorten test cycles and deliver high quality products on time. She also discusses the necessity of integrated teams and provides some proven tips successful to Web-based businesses on making this best practice a reality.
Updated: 04/06/2005
|
|
|
A Strategy for Testing C++
Compared with a procedural language such as C, the testing of C++ presents some
novel problems. This paper discusses what those problems are and outlines an
approach to the verification of C++ code. Some reference is made to implementing
these strategies using the IPL Cantata++ tool.
Updated: 04/06/2005
|
|
|
Software Testing and software development cycles
This paper outlines a number of commonly used software development lifecycle models,
with particular emphasis on the testing activities involved in each model.
Irrespective of the lifecycle model used for software development, software has to be
tested. Efficiency and quality are best served by testing software as early in the lifecycle
as practical, with full regression testing whenever changes are made.
Updated: 04/06/2005
|
|
|
An Introduction to Safety Critical Systems
This paper provides an introduction to the development of software for safety critical
systems. It is aimed to serve as a tutorial for developers who are new to the development
of software for safety critical systems, discussing the issues involved, introducing some
of the techniques available to developers, and providing an overview of how AdaTEST
and Cantata can be used to assist with the development of software for safety critical
systems.
Updated: 04/06/2005
|
|
|
One of the major software development philosophies of the Hippo project is automated testing. Unit
testing in particular has played a crucial role in the project from the beginning, and numerous unit tests
have been written to test the code.
However, not all application code is easily tested with unit tests, and web applications in particular can
prove troublesome in this regard. The goal of the Hippo testing framework team was to address some of
these issues and expand Hippo’s test framework to facilitate testing of a wider range of functionality.
Thus our broad objectives were to implement tools, technologies or frameworks to make it easier for the
other developers to test their code.
Within this scope, our prime objective was to simplify testing of the presentation layer of the application.
Our goal was to provide a thin layer between the developer and a web-testing framework such as
HttpUnit that would facilitate rapid deployment of unit tests against generated HTML. While Hippo uses
Tapestry for its web development framework, it was important to remain independent of the
implementation of this layer of the application.
Updated: 04/05/2005
|
|
|
Test Process Listings
|
|
Total:
44 | Displaying: 1 - 10 | Pages: 1 2 3 4 5 >> |
|
|
