Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "TPTP Test Framework Overview"
m (→Meeting Links and Presentation Slides) |
(→Meeting Links and Presentation Slides) |
||
| Line 25: | Line 25: | ||
===Meeting Links and Presentation Slides=== | ===Meeting Links and Presentation Slides=== | ||
[http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html TPTP Testing Strategy] | [http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html TPTP Testing Strategy] | ||
| + | [http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.hyades.test.doc.user/concepts/ccommontestingtasksandconcepts.htm Common Testing Tasks and Concepts] | ||
| + | |||
| + | [http://www.eclipse.org/tptp/home/documents/communityresources.php#test General Test Documents] | ||
[[Media:TPTP_Test_Project_Paul_Slauenwhite.zip]] | [[Media:TPTP_Test_Project_Paul_Slauenwhite.zip]] | ||
Revision as of 15:11, 12 October 2007
COSMOS/TPTP Test Meeting Notice
| Meeting Title: | Conference Call on COSMOS/TPTP Testing Framework |
| Description: | Paul Slauenwhite will give a talk surrounding the TPTP testing tools so that the COSMOS community can have a better understanding of the test facilities that TPTP provides. Paul is the project lead for the TPTP Testing Tools Project and is the Chairperson of the TPTP Architecture Group. |
| Day & Time: | Friday Oct. 12th, 1400 EST / 2pm EST |
| Toll-free Dial-in number: | +1 (866) 245-5059 |
| Local Dial-in number: | +1 (416) 343-2607 |
| International Dial-in: | +1 (800) 4444-1010 |
| Passcode: | 2771920 |
Meeting Links and Presentation Slides
TPTP Testing Strategy Common Testing Tasks and Concepts
Media:TPTP_Test_Project_Paul_Slauenwhite.zip
Questions & Answers
Q: If we already have standard JUnit tests can we convert these tests to TPTP JUnit tests?
A: Yes this is possible. Refer to the Eclipse help (Importing Junit Tests)
Q: Are there any recommended best practices to organize test suites and test execution files? Are there naming conventions that should be used when naming testsuites?