If you do:
```
$ arc unit --everything
...
FAIL PhabricatorCelerityTestCase::testCelerityMaps
Assertion failed, expected 'true' (at PhabricatorCelerityTestCase.php:32): When this test fails, it means the Celerity resource map is out of date. Run `bin/celerity map` to rebuild it.
ACTUAL VALUE
false
...
```
It can happen that it helps you in detecting that you need to run Celerity.
But, if you edit a CSS file, it can happen that this unit test is just skipped and marked as green light, like it happened here:
{D25088}
It says: `Lint Not Applicable` and Harbormaster completed the build:
{B165}
Saying "passed":
https://we.phorge.it/harbormaster/build/165/
== What happens now ==
I touch CSS files.
So, it seems, `arc diff` calls `arc unit`, and then `arc unit` does not runs the unit tests related to Celerify.
== What should happen instead ==
I touch CSS files.
So `arc diff` calls `arc unit`, and then `arc unit` runs the unit tests related to Celerify.
Note that this is the name of this specific unit test:
```
PhabricatorCelerityTestCase::testCelerityMaps
```
== List of some known cases ==
Feel free to add a path here, if you toched that file, but the `arc lint` didn't say anything:
```
webroot/rsrc/js/application/diffusion/DiffusionLocateFileSource.js
```