In Partnership with AOL Search
 
Please do not submit sites dealing with testing software or services for testing software to this category.
Service companies covering Software Testing without focus on special topics or tools.
Please submit only sites containing alphabetical or classified lists of resources about software testing to this area.

Please note: The ODP will list one domain as few times as possible, especially if the categories are rather closely sited. So if your site offers comprehensive testing information, submit it to the superordinated category only.

This catetory features link lists and other resources concerning software testing.
What''s appropriate here are products focused on testing E-Commerce sites and information about requirements, processes, and issues specific to E-Commerce site testing. General testing information should be submitted to the parent category.

Please note: The ODP will list one domain as few times as possible, especially if the categories are rather closely sited. So if your site offers comprehensive testing information, submit it to the superordinated category only.

E-Commerce testing encompasses testing of WWW sites for functionality, reliability, and performance, with a particular focus on testing sites that sell products or services online.
This category is designed for submitting sites that include software testing related resumes, career information and job postings.

Please note: The ODP will list one domain as few times as possible, especially if the categories are rather closely sited. So if your site offers comprehensive testing information, submit it to the superordinated category only.

Software Testing related jobs and recruiting sites.
Please do submit site to this category dealing with load testing, stress testing and performance testing.

Please note: The ODP will list one domain as few times as possible, especially if the categories are rather closely sited. So if your site offers comprehensive testing information, submit it to the superordinated category only.

Load testing is the act of testing a system under load. In software engineering it generally refers to the practice of modeling the expected usage of a program by simulating multiple users accessing the program's services concurrently. As such, this testing is most relevant for multi-user systems, often one built using a client/server model, such as web servers. However, other types of software systems can be load-tested also. For example, a word processor or graphics editor can be forced to read an extremely large document; or a financial package can be forced to generate a report based on several years' worth of data. When the load placed on the system is raised beyond normal usage patterns, in order to test the system's response at unusually high or peak loads, it is known as stress testing. The load is usually so great that error conditions are the expected result, although there is a gray area between the two domains and no clear boundary exists when an activity ceases to be a load test and becomes a stress test. There is little agreement on what the specific goals of load testing are. The term is often used synonymously with performance testing, reliability testing, and volume testing.
This category focuses on software testing tools covering more then one testing field. Tools dedicated to only one field are to be submitted in the respective testing category.

Testing does not include logging, debugging or bug tracking. Tools which only offer such functions should be submitted to the suitable categories, maybe to category of the programming language or component framework they cover.

Tools that may only be used for testing Java or Python programs are to be submitted in the responsible subcategories. Generic test tools implemented in Java or Python, e.g. a tool for code coverage analysis in Java and another programming language, still belong here. Sites covering hardware testing equipment and network devices testing are to be submitted to their respective categories.

Testing tools help to plan, automate, speed-up and standardize software tests. Thus, especially in large projects cost reduction within the development process is possible due to fewer product failures and cheaper test processes.
Please submit test management and test planning related sites here.

Sites which cover other topics as well should be submitted to the superordinated category. Alternatively, if a site features mainly tools which do not only offer test management, it should be submitted to the Products and Tools subcategory of software testing.

Test management deals with organizing test procedures and provides tools to store, categorize and plan tests.
Websites should generally only be listed in one subcategory of Computers: Programming: Software Testing. Which one depends on what the website and/or company behind the website specializes in.
This category is for companies offering custom or standardized training in software testing.
Please submit sites solely dealing with unit testing to this category. Sites also covering other testing topics are better suited in the subordinated category.
A unit test is a procedure used to verify that a particular module of source code is working properly. The idea about unit tests is to write test cases for all functions and methods so that whenever a change causes a regression, it can be quickly identified and fixed. Ideally, each test case is separate from all others. Unit testing is mostly done by the developers and not by end-users. The concept is part of the Extreme Programming method of software engineering. Various unit testing frameworks, based on a design by Kent Beck, have come to be known collectively as xUnit, and are available for many programming languages and development platforms. Unit testing is the building block to test driven development (TDD).
Please submit only sites dealing with user interface testing in this category. Sites also dealing with other topics of software testing may be better suited in the superordinated category.
User interface testing tries to determine correct application behavior by entering test data via its user interface, checking valid reactions thereafter. User interface testing usually may not prove proper implementation of software functions since the application under test is often tested as a black box. Tools used for this category of testing are frequently implemented as Capture-Replay tools.
Copyright © 1998-2014 AOL Inc. Terms of Use
Last update: Monday, May 12, 2014 12:48:02 PM EDT - edit