{"id":468,"date":"2012-08-14T10:47:37","date_gmt":"2012-08-14T08:47:37","guid":{"rendered":"http:\/\/www.pellissier.co.za\/hermien\/?p=468"},"modified":"2012-08-14T10:47:37","modified_gmt":"2012-08-14T08:47:37","slug":"migrating-my-mind-to-maven-part-7-functional-testing","status":"publish","type":"post","link":"https:\/\/www.pellissier.co.za\/hermien\/?p=468","title":{"rendered":"Migrating my Mind to Maven (Part 7) \u2013 Functional Testing"},"content":{"rendered":"

Functional testing with JellyTools<\/a> is fairly unfamiliar territory for me, so this morning I decided to spend some time to learn how it works with a Maven-based NetBeans Platform Application. JellyTools is a library based on Jemmy<\/a>, which allows you to manipulate GUI components during automated functional testing.<\/p>\n

My first attempt at following the Writing JellyTools Tests Guide<\/a> almost<\/em> succeeded. I created a JUnit test in one of my modules and modified it according to the guide. I also added a test dependency on org.netbeans.api:org-netbeans-modules-jellytools-platform. The test compiled and was executed as expected, but the error message returned by the test was that the class org.netbeans.Main was not found. <\/p>\n

So I decided to try moving it to the application module. And that did the trick!<\/p>\n

Now I have the following test class in my application module:<\/p>\n

[java]import java.util.logging.Level;
\nimport junit.framework.Test;
\nimport org.netbeans.jellytools.JellyTestCase;
\nimport org.netbeans.jellytools.TopComponentOperator;
\nimport org.netbeans.jemmy.operators.JButtonOperator;
\nimport org.netbeans.junit.NbModuleSuite;<\/p>\n

public class FirstScreenTest extends JellyTestCase {<\/p>\n

private JButtonOperator _btn;
\n private TopComponentOperator _tc;<\/p>\n

public FirstScreenTest(String name) {
\n super(name);
\n }<\/p>\n

public static Test suite() {
\n NbModuleSuite.Configuration conf =
\n NbModuleSuite.createConfiguration(FirstScreenTest.class).
\n clusters(“.*”).
\n enableModules(“.*”).
\n failOnException(Level.INFO).
\n failOnMessage(Level.SEVERE);
\n conf = conf.addTest(“clickButtonTest”);
\n return NbModuleSuite.create(conf);
\n }<\/p>\n

public void clickButtonTest() {
\n System.out.println(“test case: click button”);
\n _tc = new TopComponentOperator(“TC”);
\n _btn = new JButtonOperator(_tc, “Button”);
\n _btn.push();
\n }
\n}[\/java]<\/p>\n

When I test the application (right-click on the application project and choose Test), the GUI is started up and the first button on the first screen is successfully pushed by the testing framework. \ud83d\ude42<\/p>\n

Useful Links<\/strong><\/p>\n