[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #18597 [Quality Assurance and Testing]: Enhance performance timing tests for esr45
#18597: Enhance performance timing tests for esr45
--------------------------------------------+-----------------------
Reporter: gk | Owner: boklm
Type: task | Status: new
Priority: Medium | Milestone:
Component: Quality Assurance and Testing | Version:
Severity: Normal | Resolution:
Keywords: ff45-esr, TorBrowserTeam201604 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------------+-----------------------
Comment (by gk):
Replying to [comment:2 boklm]:
> > c) write a corresponding test for the User Timing API (we had #16336
for disabling the preference).
>
> I updated the resource-timing test to also check that the mark() and
measure() methods from the User Timing API cannot be used:
> https://gitweb.torproject.org/boklm/tor-browser-bundle-
testsuite.git/commit/?id=26d22e7cde628c1bb9eb04a0f258dc31d48194b2
>
> When setting dom.enable_user_timing to true, the test fails as expected.
Could we put that in an own test, test_user-timing.py for example? It
seems to me having separate tests covering these separate APIs makes it
both easier to understand what is going on and to test differences in
those APIs.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18597#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs