linting of the test files?

[ernst-at-tv2]

Are there any plans to implement linting of the test files?

sort of like:

• every it "should" {} block should contain a run command
• every it "should" {} block should contain at least one of either verify or endstate
• every file should end with stats (to exit with the correct error code)

[landro]

no, not really. It would be better to solve this avoiding this altogether, by adding some kind of required meta "boiler plate"/setup style code. That will break the API, but it would probably be no big deal for users of the framework to adapt. fre. 5. apr. 2019 kl. 09:41 skrev ernst-at-tv2 <notifications@github.com>:

…

Are there any plans to implement linting of the test files? sort of like: - every it "should" {} block should contain a run command - every it "should" {} block should contain at least one of either verify or endstate - every file should end with stats (to exit with the correct error code) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#59>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACyydaWgvd6aTEIMcFB1KYxJIhGReHLks5vdv4ugaJpZM4ceWD0> .

-- BEKK Open http://open.bekk.no TesTcl - a unit test framework for iRules http://testcl.com