68c81c7375
I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ```
53 lines
1.1 KiB
XML
53 lines
1.1 KiB
XML
<?xml version='1.0' encoding='utf-8'?>
|
|
<expr>
|
|
<attrs>
|
|
<attr name="a">
|
|
<string value="foo" />
|
|
</attr>
|
|
<attr name="at">
|
|
<function>
|
|
<attrspat name="args">
|
|
<attr name="x" />
|
|
<attr name="y" />
|
|
<attr name="z" />
|
|
</attrspat>
|
|
</function>
|
|
</attr>
|
|
<attr name="b">
|
|
<string value="bar" />
|
|
</attr>
|
|
<attr name="c">
|
|
<string value="foobar" />
|
|
</attr>
|
|
<attr name="ellipsis">
|
|
<function>
|
|
<attrspat ellipsis="1">
|
|
<attr name="x" />
|
|
<attr name="y" />
|
|
<attr name="z" />
|
|
</attrspat>
|
|
</function>
|
|
</attr>
|
|
<attr name="f">
|
|
<function>
|
|
<attrspat>
|
|
<attr name="x" />
|
|
<attr name="y" />
|
|
<attr name="z" />
|
|
</attrspat>
|
|
</function>
|
|
</attr>
|
|
<attr name="id">
|
|
<function>
|
|
<varpat name="x" />
|
|
</function>
|
|
</attr>
|
|
<attr name="x">
|
|
<int value="123" />
|
|
</attr>
|
|
<attr name="y">
|
|
<float value="567.89" />
|
|
</attr>
|
|
</attrs>
|
|
</expr>
|