Community
Participate
Working Groups
Add more Test-specific terms to the TPTP Glossary. Specifically: Test Suite Test Case Datapool Artifact Location Deployment Manual Test JUnit Test JUnit Plug-in Test URL Test The content for these (and other terms) may be found in the TPTP Test documentation (Help >> Help Contents >> Testing automatically and manually ).
Ling, the test guide that Paul refers to ("Testing automatically and manually") has been renamed to "Testing applications".
Sri, are you going to take it over now?
Paul, Need definitions for these terms.
Re-assigning to me to create definations for the terms.
Paul, please review. If happy with these definitions, I will add them to the glossary. Artifact - Test artifacts associate objects such as test suites and datapools; that is, artifacts make an asset available to a test suite. Datapool - Datapools contain data that tests can use when they run. Datapools provide variable data to your tests during execution. You can add Variables (columns), Records (rows) and Equivalence Classes (groups of related Records), to define a datapool's structure. Deployment - Test deployments typically consist of a paired test artifact and test location. Through the launch configuration mechanism, TPTP interprets the pair and deploys the test artifacts on the host computer specified. JUnit Test - A unit test written in Java. In TPTP, a JUnit test generates an execution history from which a report can be generated. JUnit Plug-in Test - A JUnit test that tests a plug-in. Location - Test locations specify the computer where the test suite will run. Manual Test - A test that is run by a user who performs each step or action in the test case. Test Case - A single test. Test Suite - A collection of tests. URL Test - A test recorded from an Internet browser.
Adding the following to the TPTP Glossary: Test Case - A set of manual or automated steps for evaluating the correctness or performance of a SUT. Test Suite - A collection test cases of a specific type, for example Manual test or JUnit test. Test suites also contain the behaviour or execution sequence of the test cases. Location - The local or remote target host for the test execution where the SUT resides. Locations also contain general properties describing the target host, used during test execution. Workbench Location - The target host for the JUnit Plug-in test execution where the SUT resides. Locations also contain general properties describing the target host and workbench properties describing the target Eclipse instance, used during test execution. Artifact - Association of test assets, such as test suites and datapools, used during test execution. Test artifacts also contain general properties describing the test assets, used during test execution. Deployment - Association of artifacts and locations used during test execution. During test execution, artifacts in the deployment are deployed to the local or remote target host identified in the paired location. Datapool - Collection of variable data used by test cases during test execution. Datapools consist of equivalence classes (tables) containing variables (named and typed columns) and records (rows). Datapool variables are associated with test case input and output for substitution of equivalence classes during test execution to produce an equivalent pass or fail result. Manual Test - A type of test suite for manual testing of a SUT by a human tester. Each test case contains textual steps for manual testing of a SUT. JUnit Test - A type of test suite for automated testing of a Java application by a JUnit test class. Each test case contains a method in the generated JUnit test class containing user-implemented code for automated testing of a Java application. JUnit test suites can be created by the API Recorder. JUnit Plug-in Test - A type of test suite for automated testing of an Eclipse application by a JUnit test class. Each test case is a method in the generated JUnit test class containing user-implemented code for automated testing of an Eclipse application. URL Test - A type of test suite for automated testing of a Web application by a JUnit test class. Each test case is a method in the generated JUnit test class containing a HTTP request for automated testing of a Web application. URL test suites can be generated by the HTTP Recorder. Automated GUI Test - A type of test suite for automated GUI testing of an Eclipse application. Each test case contains a macro and optional verification points for automated GUI testing of an Eclipse applications. Automated GUI test suites can be generated by the AGR. HTTP Recorder - Proxy-based recorder for capturing HTTP requests and responses from user interaction with a Web application using an Internet browser. Recordings may be converted into URL test suites for automated testing of a Web application. AGR - Automated GUI Recorder - Recorder for capturing GUI interactions with an Eclipse application. Recordings may be converted into Automated GUI test suites for automated GUI testing of an Eclipse applications. API Recorder - Recorder for capturing API invocations of a Java application based on user-defined filters (package/class/method/signature). Recordings may be converted into JUnit test suites for automated testing of a Java application. SUT - System Under Test. The software application or system tested by one or more test cases in a test suite. ASF - Automatable Service Framework - An automatable test execution service for launching tests programmatically via scripts (for example, shell and ANT) and external applications (for example, Java). Requesting review from Test Project committers.
Test Project Committers: Please review these definitions and edit/append as required.
Modified sentences: Artifact - Association of ****deployable**** test assets, such as test suites and datapools, used during test execution. Test artifacts also contain general properties describing the test assets, used during test execution. JUnit Test - A type of test suite for automated testing of a Java application by a JUnit test class. Each test case ****matches**** a method in the generated JUnit test class containing user-implemented code for automated testing of a Java application. JUnit test suites can be created by the API Recorder. SUT need to be defined earlier since it is used in other definitions.
Additional modifications: Automated GUI Test: A type of test suite for automated GUI testing of an Eclipse application. Each test case contains a macro script and optional verification points. Automated GUI test suites are generated by using the recording feature in the AGR. AGR - Automated GUI Recorder: A testing tool used for regression testing of Eclipse applications. The AGR allows a user to record and playback interactions with the GUI as well as write verification hooks to verify the state of the UI at test time.
Modifications: Workbench Location - The target host for the ***workbench based*** test execution where the SUT resides. ***Examples of workbench based test types include the JUnit Plug-in test type and the Automated GUI test type.*** Locations also contain general properties describing the target host and workbench properties describing the target Eclipse instance, used during test execution. JUnit Plug-in Test - A type of test suite for automated testing of an Eclipse application by a JUnit test class. Each test case is a method in the generated JUnit test class containing user-implemented code for automated testing of an Eclipse application. When executed, JUnit Plug-in tests are run within the context of a newly launched Eclipse Workbench. ASF - Automatable Services Framework - An extensible framework for exposing TPTP functionality to consumers outside of the Eclipse workbench. Examples of available services include execution of tests, interrogation of results and publication of reports. Consumers may invoke ASF services from the commandline, from ant scripts or from Java applications.
Modification: Datapool - Collection of variable data used by test cases during test execution. Datapools consist of equivalence classes (tables) containing variables (named and typed columns) and records (rows). ****Data from Datapool variables are used to replace hard-coded input and expected output data in test cases, thus "data-drive" the test. Equivalence classes are usually used to group input data that generate an equivalent pass or fail result.**** Addition: Test Log - An .execution file generated during test run to record test execution results and detailed events happened during execution. Test Log Viewer is used to read test logs.
Add: Test Log - Documents the execution of a test with time stamps and other information, including data regarding deployment, location, individual and overall test verdicts, and test execution event history. Recorder Control - Provides a convenient user interface for starting an HTTP Recording and observing the status of the recorder when it is activated. Also provides a means for manually stopping the recording when desired.
Modification: HTTP Recorder - Proxy-based recorder for capturing HTTP requests and responses from user interaction with a Web application using an Internet browser. Recordings are automatically converted into URL test suites by the URL Test Generator for automated testing of a Web application at the end of a recording session. URL Test - A type of test suite for automated testing of a Web application by a JUnit test class. Each test case is a method in the generated JUnit test class containing a HTTP request for automated testing of a Web application. URL test suites can be generated from HTTP recordings by the URL Test Generator. Addition: URL Test Generator - Generates URL Tests from HTTP recordings. This is called automatically by the HTTP Recorder after the recording ends to generate a URL Test. It can also be executed manually.
(In reply to comment #13) Thanks Mark. Can you set the review flag to '+'?
Changed review flag to '+'
New definitions checked-in to CVS (HEAD).
Verified on the TPTP web site.
Test.Web being moved to TPTP.Web
