Fixed so that timing will always use native Date for rare cases

[strille]

Since the user might mock Dates in tests, KarmaReporter saves a reference to the native Date and uses that reference for measuring duration. The problem is that it only works when users follows best practises when writing tests.

If a user writes a "bad" test where the Date is mocked in the body of a decribe instead of inside an it or beforeEach, the Date is already mocked by the time KarmaReporter is called.

By saving the reference at the time adapter.js is executed instead of when KarmaReporter is called, this problem is prevented.

Nothing prevents a developer from writing:

describe('foo', function () {
    jasmine.clock().mockDate(new Date(0));
    it('bar', function () {
    });
}

Before the change in this PR, a test like the one above would cause the duration of the test to be reported incorrectly. If the time is reported as negative, then all sorts of thouble can happen down the line.

We ran into issues where a report file generated by karma-sonarqube-unit-reporter containing 4500+ tests was ignored by Sonarqube because a duration in the xml was negative.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[strille]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.