COMP285/COMP220 Lab test (Ant and Junit)

It is recommended (but you don’t have to) use Eclipse to edit the source files.

For this test you must produce a build directory and ant build file.

You must also produce a Junit java test file call RegistrationHelperTest.java with tests to test the code found here. A stub form of this test file is provided for you, please remember to change the method getStudentID() so that it returns your 8-digit student id.

There are 2 files, RegistrationHelper.java and RegistrationHelperTest.java

NOTE The RegistrationHelper java you have been contains no bugs. So all tests should pass.

RegistrationHelper.java is the file you will be testing and it should be copied into the src directory.

IMPORTANT The package name for all the files in this project needs to be labtest, so please copy the files into the correct source directories. So RegistrationHelper.java needs to be in src\labtest

Here is the specification of the code.

There is 1 method called boolean checkUsernamePassword(String username, String password)

The following are the validation rules:

The test source files for this lab test should be stored in test\src.

There should be a directory called build\classes where the classes are stored. (Please turn over)University of Liverpool Lab test assessment

Your ant file should compile Main.java and RegistrationHelperTest.java and then leave the result in build\classes.

Submission

A zipped up file which is the whole build directory, the name of this file should be named

LabtestXXXXXX.zip where XXXXXXX is your long University id number.

This zipped file must contains.

A build.xml file which compiles makes output directories if needed, copies files from test\targetClaases to build\classes, builds the test code and runs the Junit tests and also produces reports about the tests in XML and HTML.

The directory structure should have the following directories 

build\classes Containing all classes for the application (test and target classes)

Marking 

The marks are assigned as follows:

Note for the “Ability to reveal bugs” part of your assessment you tests must do the following:

TIPS Make each assertion test case test only 1 issue at a time. Check all boundaries, edge cases.