Page MenuHomePhabricator

Rough version of configuration driven unit test engine
ClosedPublic

Authored by joshuaspence on Jul 7 2015, 2:07 PM.
Tags
None
Referenced Files
F14077204: D13579.diff
Thu, Nov 21, 9:55 PM
Unknown Object (File)
Wed, Nov 20, 6:36 PM
Unknown Object (File)
Wed, Nov 20, 11:03 AM
Unknown Object (File)
Sat, Nov 16, 10:59 AM
Unknown Object (File)
Tue, Nov 12, 7:24 AM
Unknown Object (File)
Tue, Nov 12, 2:22 AM
Unknown Object (File)
Sat, Nov 9, 9:32 AM
Unknown Object (File)
Fri, Nov 8, 2:13 PM

Details

Summary

Ref T5568. As discussed in IRC. This is very rough and not widely useable, but represents a solid first step.

Test Plan

Ran arc unit with a bunch of flags.

Diff Detail

Repository
rARC Arcanist
Branch
master
Lint
Lint Passed
Unit
Test Failures
Build Status
Buildable 7268
Build 7575: [Placeholder Plan] Wait for 30 Seconds
Build 7574: arc lint + arc unit

Event Timeline

joshuaspence retitled this revision from to Rough version of configuration driven unit test engine.
joshuaspence updated this object.
joshuaspence edited the test plan for this revision. (Show Details)
joshuaspence added a reviewer: epriestley.
epriestley edited edge metadata.
epriestley added inline comments.
src/unit/engine/ArcanistConfigurationDrivenTestEngine.php
8

Maybe only true if at least one configured engine supports --everything.

70–73

Could we just do the type check first, and simplify this a bit?

121

I think we should move away from support for this (and "postponed" linters) -- these models never really made sense, and Harbormaster is on the horizon now. Fine to maintain support if it's "free", but feel free to just drop it if it's non-free, too.

126

At some point, maybe we should emit a warning here if an engine doesn't support --everything, to reduce surprise when --everything does not really mean --everything.

129

Consider type checking the results, similar to D13486, to place blame on bad engines more clearly.

151

(Is this essentially identical to something in the Lint engine?)

This revision is now accepted and ready to land.Jul 7 2015, 3:34 PM
joshuaspence marked an inline comment as done.

Only support --everything if at least one of the configured test engines supports it

joshuaspence marked an inline comment as done.

Rename class for consistency

joshuaspence marked an inline comment as done.

Add a bunch of TODOs

joshuaspence edited the test plan for this revision. (Show Details)

We're using this as part of our development workflow now and it's nice. It would be nice if it made use of our phpunit.xml configuration, but we can work around that for now. I hope this lands on master soon.

Thanks @joshuaspence!

This revision was automatically updated to reflect the committed changes.