US3 User signup persistence o "As a grocery store customer, I want the app to remember my preferred username and email address, so that I can build loyalty points and get special offers and coupons."

o Acceptance tests:

AT6: Given a user enters a valid preferred username and email address, when the user presses the signup button, then the user's preferred username and email address is saved in the database.

AT7: Given a user that has already clicked signup, when the user loads the application the next time, then the application does not ask the user to signup again.

please briefly explain the following two questions.

question 1: how would you implement these methods with test-driven development?

question 2: How would you write tests that determine whether the user's preferred username and email address were properly saved or loaded to or from the database without actually having Curby's code?