They should be passing, except for the Groovy debug tests. Go to the Arguments tab and add the following to the VM arguments: -Xmx1024M -XX:PermSize=64M -XX:MaxPermSize=128M.Choose the launch configuration you just created in step 2.Select the arrow next to the Debug icon in the toolbar -> Debug configurations.You must change your launch configuration and augment memory settings.This will likely fail due to memory constraints (you may even want to end the test if it is taking too long before even starting).Right-click -> Run as -> Junit Plugin Tests.If you would like to contribute any significant piece of code to the Grails-IDE project, you will be required to include test cases. Once the test projects are compiling cleanly inside of Eclipse, you can now run the tests. SWT-bot is available form this update site: Keep this test suite closed unless you have SWT-Bot installed. Also, if you want these tests to compile you will need to install swt-bot, which is our UI testing framework. This test suite is not necessary to run unless you know you are working in this area. This test suite is generally a more fragile and may not pass on Windows. .test.ui.AllGrailsUITests: tests wizards, window state, and other UI.Usually takes about one hour to run completely since it downloads multiple versions of grails, issues many commands, starts and stops servers, etc. This suite is of general interest and should be run to ensure correctness. ![]() .test.AllGrailsTests: tests the core Grails functionality including creating projects, editor support, launching, debugging, etc.Getting the tests to compile inside of Eclipse Use this update site after Eclipse Juno is released: Use this update site and install the Eclipse SDK (this site will be available until the Eclipse Juno release at the end of June 2012): Since GGTS does not ship with the source code for Eclipse projects (Eclipse Platform, JDT, JFace, SWT, etc), you must install them separately. Important also, close the 20 plugin unless you are working on Grails 2.2.x or later, which requires Groovy 2.0. Note that there are projects that will not compile unless you have m2e (Maven-eclipse support) installed in your Eclipse. Groovy-Eclipse: Eclipse-Integration-Commons: information on setting up the Groovy-Eclipse dev environment is available here.Cloning these repositories will not only make the source code available for these projects, but it will also make (most of) the Grails-IDE test projects compile cleanly inside of Eclipse: Unless you explicitly installed the source code, it will not be available to browse. Getting the remaining Grails-IDE related source code into Eclipseīy cloning only the grails-ide repository, and not eclipse-integration-commons or groovy-eclipse, the Grails-IDE projects will resolve against the binaries of your Eclipse installation (aka the target platform). Launch a runtime workbench (in debug mode if you want to be able to use the debugger) to verify that your workspace is correctly configured.If you want to compile and run the tests inside of Eclipse, you will need to clone the eclipse-integration-commons and the groovy-eclipse projects into your workspace. The errors come from dependencies on test projects located in other git repositories. There will be errors in the following test projects.import all projects into the workspace (optional- use egit to do the importing).Clone the grails-ide git repo (optional- use egit to do the cloning). ![]() Starting from an eclipse base is possible but extra software (like Groovy/Eclipse) would need to be installed.
0 Comments
Leave a Reply. |