ToDo.txt

// To do:

// test icon_colors.js

// determine a way to return element IDs of all people in a house, step through the array, and act accordingly depending on the test case - proceed? Or exit and try another house?

// need to determine how many primary targets there are in the selected household

// make fullLogin method take parameters for username and password - i.e. so you can log in with whoever you want in the test.

// complete a walkbook and inspect the close/leave open dialogue.  Compare Android and iOS & add to elements file.

// investigate - walkbook list ordering is different in Android - could be due to location?  Figure out how to programmatically simulate location if possible.




	Later:
	// create a credentials file?  Test creds shouldn't be sensitive.  Place sensitive credentials in file and add to .gitignore.

	// if possible figure out a way to access an element by part of its id - see todo comments in code.  Figure out promise-utils file.

	// elementOrNull command - utilize in fullLogin method:

		Retrieve an element avoiding not found exception and returning null instead:
		elementOrNull(using, value, cb) -> cb(err, element)
		TRY THIS IN fullLogin instead of the nested functions to check if rememberMe is checked.

	Ongoing:
	// Break up tests into folder and subfolders

	Questions for Bruce: 
		Understanding Promise Utils functions


// Miscelaneous

	// try these for finding elements by a part of their id:

	  .elementByXPath('//*[(contains(id()\'prim_btnRemaining\')],600000)
	  .elementByXPath('//*[contains(@id,\'cellHouse_8\')]')
	  .elementByXPath('//*[contains(@text,\'cellHouse_8\')]')
	  .elementByXPath('//*[contains(@checked,\'false\')]')

	// wait for an element by one of two things:
	  .waitForElementByXPath( '//UIAApplication[1]/UIAWindow[1]/UIAElement[2] | //*[ @text=\'View Later\' ]', 600000 )