| Summary: | Meta tag for Tests with Empty & Single Empty Line Expectation Files | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ahmad Saleem <ahmad.saleem792> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | aakash_jain, ap, bfulgham, jbedard, ryanhaddad |
| Priority: | P2 | ||
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 248037 | ||
|
Description
Ahmad Saleem
2022-11-30 04:11:36 PST
I don't think that we should do this. Having a second way to declare expectations will be forever confusing to engineers, and will complicate webkitpy code. It's better to only have one place to look at than multiple. We do have a similar feature for test options, and the experience of having it is not great. The reason why we still have it is that there isn't an alternative way to set these test options. Notably, it's not using a <meta>, but custom syntax, because run-webkit-tests doesn't understand HTML. |