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 "Scout/Concepts/Test"
(First version of the page.) |
(→RT) |
||
| Line 3: | Line 3: | ||
This Page describes the architecture we want to obtain for the Scout Test Infrastructure (Testing support: how to test a scout application, but also unit test for Scout RT and SDK). See [http://www.bsiag.com/scout/?p=635 Scout Roadmap] for more information. | This Page describes the architecture we want to obtain for the Scout Test Infrastructure (Testing support: how to test a scout application, but also unit test for Scout RT and SDK). See [http://www.bsiag.com/scout/?p=635 Scout Roadmap] for more information. | ||
| − | + | ''Please do not change the title of the sections'' | |
| Line 27: | Line 27: | ||
== RT == | == RT == | ||
| + | The RT Code contains some classes used before JUnit (ITest, AbstractClientTest, AbstractServerTest, ...). This approach should no longer be used. | ||
| + | === TODO === | ||
| + | * {{FixedBug|397085}}: <s>Mark legacy testing support as deprecated</s> | ||
Revision as of 13:35, 14 January 2013
The Scout documentation has been moved to https://eclipsescout.github.io/.
This Page describes the architecture we want to obtain for the Scout Test Infrastructure (Testing support: how to test a scout application, but also unit test for Scout RT and SDK). See Scout Roadmap for more information.
Please do not change the title of the sections
Demo
BSI has a small Demo Application (Client-side only) that displays all the fields. For the moment this application is closed source.
This application is useful to display all possibilities offered by the fields (common configuration for each field). There is no need to have this in the eclipse repository (no need for IP-Clear). Therefor the idea is to refactor the application publish it on github.
Nice to have: For each demonstrated field, we want to have a link to the GitHub java source code page.
Branch organization on GitHub should be the same as in the Eclipse Repository.
TODO
- Find a name for the project: com.github.widgets-demo or something like that.
- Create the repository in GitHub
- Create a POC
- one page for one field
- with link to the source code at Git-Hub
- built with Maven Tycho
- create the rest of the pages (for the other pages) == migration of the current test application to the new widgets-demo application.
- mention the project in the scout book
RT
The RT Code contains some classes used before JUnit (ITest, AbstractClientTest, AbstractServerTest, ...). This approach should no longer be used.
TODO
- bug 397085:
Mark legacy testing support as deprecated