cxong / cbehave

A Behavior Driven Development Framework for C

Hi 👋, I'm congusbongus

A hobbyist game developer and occasional open source tinkerer

• 🔧 I maintain open source games like C-Dogs SDL and OpenCrystalCaves
• 📝 I write articles on https://cxong.github.io

Mastodon

cbehave's Issues

Remove numbers from FEATURE macro

i.e. adopt cspec's convention of referring to features by name only

This also means the name must be a proper C token - i.e. can't have spaces in it. Allow a free text description instead.

Remove SCENARIO_END

This can be done by having GIVEN create a dummy scope and scenario state, which the SCENARIO_END implementation must handle.

We'll also need to implement #4 since tests may be adding feature-level code setup, which will need to also handle the dummy scope.

DESCRIPTION

Just cosmetic - a printf at the beginning of features

BACKGROUND

Use to set up some state common to all scenarios
Can be done already by inserting code into the FEATURE block, but this would be better practice, and allow GIVEN/AND syntax.

Travis CI