Update of /cvsroot/e-p-i-c/org.epic.perleditor-test In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv21948 Added Files: test.properties .cvsignore plugin.xml .classpath .project README.txt easymock.jar build.properties cglib-full-2.0.2.jar Log Message: Plug-in with automated test suites for org.epic.perleditor. See README.txt inside. --- NEW FILE: .cvsignore --- bin --- NEW FILE: .project --- <?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>org.epic.perleditor-test</name> <comment></comment> <projects> </projects> <buildSpec> <buildCommand> <name>org.eclipse.jdt.core.javabuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.pde.ManifestBuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.eclipse.pde.SchemaBuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.pde.PluginNature</nature> <nature>org.eclipse.jdt.core.javanature</nature> </natures> </projectDescription> --- NEW FILE: test.properties --- # Local configuration settings for the test suites. # See README.txt. # Path to the Perl interpreter org.epic.perleditor-test.perl = /usr/bin/perl --- NEW FILE: .classpath --- <?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="src" path="src"/> <classpathentry kind="src" path="src-pde"/> <classpathentry exported="true" kind="lib" path="cglib-full-2.0.2.jar"/> <classpathentry exported="true" kind="lib" path="easymock.jar"/> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> <classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/> <classpathentry kind="output" path="bin"/> </classpath> --- NEW FILE: easymock.jar --- (This appears to be a binary file; contents omitted.) --- NEW FILE: plugin.xml --- <?xml version="1.0" encoding="UTF-8"?> <?eclipse version="3.0"?> <plugin> </plugin> --- NEW FILE: cglib-full-2.0.2.jar --- (This appears to be a binary file; contents omitted.) --- NEW FILE: build.properties --- source.. = src/ output.. = bin/ bin.includes = plugin.xml,\ META-INF/,\ . jars.compile.order = . --- NEW FILE: README.txt --- EPIC Automated Test Suites -------------------------- The pseudo-plug-in org.epic.perleditor-test contains two test suites for org.epic.perleditor: 1. Tests defined in the source folder "src" are plain old unit tests for Eclipse-neutral code. They can be run using the JUnit run configuration. 2. Tests defined in the source folder "src-pde" are end-to-end tests that execute in a self-hosted Eclipse workbench. They can be run using the PDE JUnit run configuration. Both test suites should be run with the following VM arguments: -Xmx256M -ea -Dorg.epic.perleditor-test.properties=<path to test.properties> Moreover, the tests from "src" should be run with location of org.epic.perleditor-test as their working directory. The file test.properties contains local configuration settings and has to be updated to match your environment. A sample version of this file is kept in CVS for reference. The folder test.in contains resources needed by tests (such as expected test results). The tests from "src-pde" require a preconfigured workspace as their fixture. This workspace is kept in CVS (org.epic.perleditor-test/workspace). The path to this workspace must be specified in the PDE JUnit run configuration. The test workbench is launched with only EPIC plug-ins (and their dependencies). (Some of) the "src-pde" tests simulate user input through Display.postEvent and are therefore fragile: they will fail if you interact with the GUI while they are running. Otherwise, they should run clean. Last but not least, the present test suites are very incomplete. Keep this in mind when making decisions based on their results. Questions? -> jp...@us... |