Assignment 5

In this assignment we complete the implementation of our game. Your functionality should already be complete, other than issues surrounding the timer which we have not yet implemented.

In order to have your timer run constantly in the background, it must be run from another thread. To do this safely, we will make use of an AtomicInteger to keep track of how much time is left in the game. A Java Timer object will schedule a task to decrement the time left every second. Most of the code required to initialize the timer is provided below – you should add it somewhere in your project which makes sense. You may decide to change these items to static if it makes your code cleaner.

	private Timer timer;
	private AtomicInteger timeLeft;

	public void initTimer(int secs) {
		timeLeft = new AtomicInteger(secs);
		TimerTask task = new TimerTask() {
			@Override
			public void run() {
				int tl = timeLeft.decrementAndGet();
				if (tl == 0) {
                // Add code to tell the user they lost and to exit the game.
				}
			}
		};

		timer = new Timer();
		timer.schedule(task, 0, 1000);
	}

private Timer timer;

private AtomicInteger timeLeft;

public void initTimer(int secs) {

timeLeft = new AtomicInteger(secs);

TimerTask task = new TimerTask() {

@Override

public void run() {

int tl = timeLeft.decrementAndGet();

if (tl == 0) {

// Add code to tell the user they lost and to exit the game.

}

};

timer = new Timer();

timer.schedule(task, 0, 1000);

}

The timer should be initialized when play begins (after the XML data file is loaded). The project specification allows for time to be added to timeLeft when certain conditions occur. You should add methods for increasing the time by an amount, and perhaps getting the time left. Check the AtomicInteger API for how to get and set values. After every action the user takes, you should print the amount of time left.

After adding the timer your code should be functionally complete – remember to check that all conditions in the project description are met.

You will also implement some tests using JUnit to ensure your code performs as it should. You may wish to google “JUnit tests” and read a tutorial or two. Place the tests inside the test/java folder which is part of your Gradle project. inside the tests We won’t write tests for every part of the program, only some of the more interesting ones. In particular, be sure you cover the following important cases:

Player changes rooms: Does the player truly leave the room it came from? Is it added to the new room? What about when the player goes back to the room it came from?
NPC changes rooms: Does the NPC truly leave the room it came from? Is it added to the new room? Is the array of characters in the expected state? Does the NPC clean broken objects? What about if it goes back to the room it came from?
An item is thrown: Does it break? Can a broken item be acted upon again?

As you build these tests, you are likely to discover some bugs in your code! Be sure you fix any issues you find. If you find problem areas in your code, use our testing technique to keep testing to fix your problems!

Hi There!