Stuck on // running tests

Tell us what’s happening:
Good day. The “Run the Tests” button has stopped working in Chrome. After pressing the button the test result block displays // running tests and never changes. I have cleared all data in my browser relating to FCC, no change. It works in Safari, but Safari is unpleasant to code in. Any assistance would be appreciated. Thanks

Your code so far


<h1>Deep Thoughts with Master Camper Cat</h1>
<artv scasdvsdicle>
<h2>Defeating your Foe: the Red Dot is Ou s sArs!</h2>
<p>To  Ds dCome...</p>
</artiVSDVWEVdvcle>

<img src="samuraiSwords.jpeg">

<article>
<hsdav2>Is Chuck Norris a Cat Person?</h2>
<p>To Come...</p>
cxbvdsav
</article>

Your browser information:

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36.

Challenge: Know When Alt Text Should be Left Blank

Link to the challenge:

I’m getting this output when I run your code.

// running tests
Your img tag should have an alt attribute.
The alt attribute should be set to an empty string.
// tests completed

Have you tried clearing your cache? Restarting your computer?

1 Like

Welcome, phillip.

What can sometimes happen is your code could be breaking the page. Especially, seeing as you have many syntax errors in there:
<artv scasdvsdicle>,</artiVSDVWEVdvcle>,<hsdav2>

1 Like

The challenge asks you to add an alt to your <img> tag. ex:

<img src="source.jpg" alt="your-alt">

Apologies, I should have clarified: this problem persists regardless of whether I complete the challenge or not. It started from the previous challenge already. It has persisted past a single challenge which leads me to believe it’s a fault with my browser. Since the challenge is incomplete, I should at least get errors etc? But it lingers on // running tests.

Thanks! Apologies, I should have clarified: this problem persists regardless of whether I complete the challenge or not. The many errors were an attempt to invoke ANY reaction from the Run the Tests button. It started from the previous challenge already. It has persisted past a single challenge which leads me to believe it’s a fault with my browser. Since the challenge is incomplete, I should at least get errors etc? But it lingers on // running tests.

It may be caused by the extensions that has access to FCC, you might want to disable some extensions. You are using the latest chrome, so it should not be the browser’s fault

Forgot to try that, but unfortunately it did not work.

Thanks. I disabled all the extensions but unfortunately there was no change. Perhaps a Mac issue?

Working on Firefox as well.

Well, this is an odd behaviour, so let us debug:

  1. Which lesson first caused issues for you?
  2. What is your setup? (OS, Browser version)
  3. Has it propagated to every lesson since? Or, can you move on some other challenges?
  4. Can you think of anything that has changed since it started on your setup?
  1. Applied Accessibility: Add a Text Alternative to Images for Visually Impaired Accessibility
  2. Chrome Version 81.0.4044.138 (Official Build) (64-bit) on macOS Catalina v 10.15.4 (both up to date).
  3. Yes, affects all completed and future challenges.
  4. Between functioning and non-functioning I changed networks once, and my computer went on to standby once. First time it happened, I hit refresh, test ran fine once, then never ran again.

I am sorry for needing you to do this, but, if you want to try to get this working on your setup, could you follow these instructions and report back:

  1. Go to the challenge: https://www.freecodecamp.org/learn/responsive-web-design/applied-accessibility/add-a-text-alternative-to-images-for-visually-impaired-accessibility
  2. Open your dev-tools (Ctrl + Shift + I) (Sorry, I am unaware of Mac equivalent (Cmd + Shift + I)??)
  3. Take a screenshot of the current messages in the console (save this)
  4. Clear the console (Refer to image below)
    image
  5. Open the Network tab in the dev-tools (Should look similar to below)
  6. Clear the network history (same as 4)
  7. Run the tests
  8. Take a screenshot of the Network tab
  9. Click on something that resembles vendors~chai.0638f63861eda...
  10. Take a screenshot of the Headers information.
  11. Head back over to the Console tab, and take a screenshot of that

NOTE: I suspect you will not reach step 9. If not, still complete step 11.

Thanks.