When I’m writing these out, I’m also writing out my investigative process. Please learn from that - that is the more valuable lessons. Good coders are good detectives.
When I press the red “14/16 Passed” button and look at the first test failing, I see:
Within the form, there is a submit
<input> with corresponding id=“submit”.
#submit should be an
<input> element : expected ‘BUTTON’ to equal ‘INPUT’ AssertionError: #submit should be an
<input> element : expected ‘BUTTON’ to equal ‘INPUT’
You have a couple of forms going on here, but when I look for the offending code, I see:
It is saying that that element you should use is
button. When I look in the docs I see that this is the form they suggest:
<input type="submit" value="Send Request">
I also see that you did something similar down below:
<input id="submit" type="submit" value="submit input">
That is what is wanted. I think that you can use a
button for that, but the user stories specifically say:
User Story #11: Within the form, there is a submit
input with a corresponding
When I fix that, that test passes.
Part of being a good dev is paying close attention to tiny details. As a dev, there have been times when I wrote perfectly working code that got rejected because I missed some silly little arbitrary requirement - that’s just part of the job.
Anyway, fix that. Then get out your magnifying glass, your deerstalker cap, and your calabash pipe and see if you can figure out the last failing test. Check back if you get stuck.
A last note - I notice that you had two things with and id of “submit”. But ids must always, always, always be unique. You are never supposed to have two things with the same id.