For the Health Metrics page accessible by the Patient, do we have to create a new JSF-based page or can we use the existing JSP page?
Honestly, I'd forgotten this was there. You can use what is there or you can rip out the existing page and replace it with a page that only includes health metrics. The latter may be easier. However, if you rip out the page you MUST document what you ripped out. You may also find that ripping out the page removes elements that you will wish you had for the project (although it will not impact your grade for HW3P3
Can I use a web driver as part of my Cucumber tests?
We would still prefer that you avoid it if at all possible. However, it is acceptable.
Do I have to have 80% coverage if I can't even test 90% of my class since it uses a FacesContext? Do I have to learn Mockito?
The answer is the same as last time - test as much as you can with documentation of what you can't test. "I ran out of time to finish my test cases" isn't a reason not to create them. "Lines X-Y require foo-bar which I cannot test using jUnit for reasons A, B, and C" (updated appropriately) is more likely to be accepted.
90% seems a bit extreme. If it really is 90% untestable you may want to discuss your implementation with the TAs (in person, via email, or via private post if you plan to include details/code).
What are the issues with the existing acceptance tests?
TestDeletedHealthRecord: Ignore, behavior is not in the use case
Weight Status in all tests: Ignore, this is part of UC16
Logging in all tests: Ignore, it's broken throughout iTrust
TestHCPLoggingAction: Nullified, it's just a log test and we're ignoring logging
BMI Values: Get close enough with height/weight inputs
BMI Format: Be reasonable: anything from an integer to .01 precision is fine