D3: Scatterplot Example fails tests

[thecodingaviator]

Describe the bug
The example given for the D3 scatter plot challenge on CodePen is failing certain tests which it should not have. Only 14 out of the required 16 tests are passing.
The failing tests are namely:
6. The data-xvalue and data-yvalue of each dot should be within the range of the actual data and in the correct data format. For data-xvalue, integers (full years) or Date objects are acceptable for test evaluation. For data-yvalue (minutes), use Date objects.
and
12. I can see that the range of the y-axis labels are within the range of the actual y-axis data.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://codepen.io/freeCodeCamp/full/bgpXyK'
2. Click on 'Run Tests'
3. Wait till the tests are completed
4. See that only 14 out of 16 tests are passing.

Expected behavior
Since it is an example for the campers to follow, they should be shown something in which all tests pass

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Windows 7 x32
• Google Chrome
• Version 70.0.3538.77 (Official Build) (32-bit)

[username1001]

There is a slight delay in the last two tests, but they did pass for me. I'm seeing 16/16.
I should probably include this:

Ubuntu 18.04

Mozilla Firefox 61.0.1 (64-bit)

[thecodingaviator]

On Chrome they're still failing

[moT01]

I was unable to reproduce this on Chrome or firefox - the last two tests do take an extra couple seconds. Want to give it one more try @thecodingaviator? Maybe try on another browser, there could be some zoom or extension settings messing with something on your browser perhaps.

[thecodingaviator]

Still failing on both Firefox and Chrome for me. Maybe someone else can have a look and this might be an issue with only me, although I'm still not sure why they're failing

[KaustubhD]

Hi,
I finally completed this challenge today and the cases were failing for me too. (14/16 passed)
The reason is difference in timezones.
The Date object taken here although made through UTC, changes to local timezone and thus producing different times as compared to the dataset.

Proposal:
I made it so it is timezone free (hopefully)
Pen Link

[thecodingaviator]

@KaustubhD Can you have a look at tests in https://github.com/freeCodeCamp/testable-projects-fcc and update the tests there to get this to work?

[KaustubhD]

Changing the tests would mean that its ok to display the data in respective time zones.
Eg. the minimum time i.e. 00:36:50 UTC becomes 06:30:18 in IST.
So essentially we are changing the data itself.
Thoughts ?

[thecodingaviator]

@KaustubhD I guess that's the best way to do it without breaking all the previous projects

[KaustubhD]

@thecodingaviator Alright then, i'll give it a shot.
While we're at it, could you look here and tell if the Y scale should be inverted or not ?

Ok, so there has been a mistake on my part. Just realised that my previous comments have just been rendered useless.
The test cases work fine, you need to update only the example project.

Can i do that ?

[thecodingaviator]

I think you should get in touch with @raisedadead about that. You'll find him on the Gitter chat room

[thecodingaviator]

@lasjorg I guess you’re looking after updating the CodePens too. Could you please chime in?

[lasjorg]

I can't reproduce it, the example project is passing all the tests for me.

[KaustubhD]

@lasjorg You can just change your system timezone and reload.

[raisedadead]

@scissorsneedfoodtoo can you validate the pen proposed here. We could update ours (to not break the links from this updated pen)?