**After a short pause the status field should turn green and tell you that the test has finished running. This does not mean the test was successful, only that it has finished running.

+

**Scenario EDT_SQL_TESTS tells you how to check the results of the test.

+

Edit org.eclipse.edt.tests.sql.jndi\EGLSource\org_eclipse_edt_tests_sql_jndi.egldd. On the Resource Bindings tab, change the JNDI name of the data source from jdbc/DerbyConnection to some other value. Press the Run Test button of SqlJndiConnectionTest and check the results of the new test. There should be many "name not found" failures while looking up the name jdbc/DerbyConnection.

Set up the compiler(s) you wish to use for the project. To do this, right click on the project in the Project Explorer and select properties. Then click on "EGL Compiler" on the properties page. Select the Java and/or JavaScript generator, depending on what is being tested and press OK.

Once compilation completes, right click on the project and select "Generate EGL Test Driver". Select either Java or JavaScript (depending on which environment you are testing).

After a short pause the status field should turn green and tell you that the test has finished running. This does not mean the test was successful, only that it has finished running.

Scenario EDT_SQL_TESTS tells you how to check the results of the test.

Edit org.eclipse.edt.tests.sql.jndi\EGLSource\org_eclipse_edt_tests_sql_jndi.egldd. On the Resource Bindings tab, change the JNDI name of the data source from jdbc/DerbyConnection to some other value. Press the Run Test button of SqlJndiConnectionTest and check the results of the new test. There should be many "name not found" failures while looking up the name jdbc/DerbyConnection.