[Webkit-unassigned] [Bug 82245] New: W3C testharness.js tests should not require an -expected.txt file

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=82245

           Summary: W3C testharness.js tests should not require an
                    -expected.txt file
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: stearns at adobe.com


https://bugs.webkit.org/show_bug.cgi?id=80709 (Convert regions parsing test to use testharness.js) added testharness.js files from the W3C and a sample test that uses this harness. It also added an -expected.txt file for the test, as this was the easiest way to integrate W3C testharness.js testing into WebKit.

This means that when we import W3C test suites, we will have to create and maintain -expected.txt files for each testharness.js test. It would be better if our test harness was able to determine whether a testharness.js test passed or failed without an extra .txt file. The data is available at the end of the test - we're just creating a .txt file to compare against the report output.

Perhaps there's something in the W3C test suite build system that we can use to identify testharness.js tests, as we do with reftest reference matching with the manifest?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.