Help talk:Pickle/Glossary

What is a skipped test, precisely defined? Same remarks apply as to the "Pending?" request.

A skipped test is a test that the underlying system has chosen to defer due to missing dependency or some other reason. It is possible to manually mark tests as skipped.

The easiest (most obvious) explanation is perhaps that the test is only partially defined, as seen by the system and not by the coder.

Perfect, thanks!

Hm, I'm not sure I completely understand yet. How can a test marked "skip" be ok or not ok? What determines whether a skipped test is ok or not?

I am having trouble understanding "A good result is one where all reported tests marked "skip" were ok."

A skip-maker can be inserted into the description for a test, that will give an unconditionally "not ok # skip" in the output. If the skip marker is added in the code after an assertion then it will give a "ok # skip" in the output.

There are two messages "pickle-test-text-skip-fail" and "pickle-test-text-skip-good".

It is (nearly) the same with the todo markers, but further processing will not be terminated.

Final state can be a bit more involved, but I'm not quite sure there is much to be gained from shifting from implicit w:Universal quantification to explicit use of both Universal quantification and w:Existential quantification. For now it is implicit universal quantification and all tests must pass.

Got it. Thanks!

It would be nice with a clear definition of what a "pending test" is, with some context. The word "pending" is currently not mentioned at all in the glossary, and I am trying to translate having only a general knowledge of software development but without knowing the specifics of this extension. Is a pending test still running, did it fail, or what constitutes a pending test exactly?

A pending test is a test that is either marked as "skip" or "todo". Such tests will be in an undetermined state until the reason for them to be marked is resolved.