Tell us what’s happening:
Your code so far
<img src="https://bit.ly/fcc-relaxing-cat" alt="A cute orange cat lying on its back.">
<p>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>
<a href="https://freecatphotoapp.com">"cat photos"</a>
<p>Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.</p>
Your browser information:
User Agent is:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36.
Challenge: Link to External Pages with Anchor Elements
Link to the challenge:
what do the failing tests say?
Look closely at the text that particular test is expecting, and then look closely at the link you are providing. Are they the same?
I will say the same thing here that I just said in another thread - tests are not very intelligent, in that they are looking for a very specific text string. The lesson tells you exactly what the test is looking for, but as a developer, we need to be very precise in what we code.
While it may seem trivial at this point, the difference between, say FTP and SFTP can be significant. When it comes to actual deployment, it’s the difference between getting to that target endpoint, and presenting your (potential client’s) guests with a
404: page not found error.