Ref T5568. Use the very-new, very-beta ArcanistConfigurationDrivenUnitTestEngine unit test engine.
Details
Details
- Reviewers
epriestley - Group Reviewers
Blessed Reviewers - Maniphest Tasks
- T5568: Support `.arcunit`, similar to `.arclint`
- Commits
- Restricted Diffusion Commit
rPbcdb7e9a2c69: Use the configuration driven unit test engine
arc unit
Diff Detail
Diff Detail
- Repository
- rP Phabricator
- Branch
- master
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 7572 Build 8184: [Placeholder Plan] Wait for 30 Seconds Build 8183: arc lint + arc unit
Event Timeline
| .arcunit | ||
|---|---|---|
| 5 | Besides the fact that there are currently only tests for code in src/, is there any other compelling reason to limit this to src/? | |
Comment Actions
I don't think there's any particular reason to limit it.
And I suppose we might eventually ship other libraries in optional/ or something, which would make limiting it not so good.
Comment Actions
No idea. If there was, say, a template application that we shipped with as a starting point for third parties and it had some example tests in it, we probably would, which seems plausible, maybe?