Closed erichstuder closed 8 months ago
Hi @erichstuder unfortunately the e2e test don't work anymore. They use the Cucumber Technology Compatibility Kit which will no longer be developed and depends on quite old packages. We plan to replace or remove the e2e test.
I removed the broken e2e tests with #272.
👓 What did I see?
I try to build cucumber-cpp according to the README.md I have installed all the dependencies correctly i think. see my Docker-Container The Container has not yet any dependencies to my project, so it can be run on its own.
Then in the container I build cucumber-cpp as advised:
In the last step
cmake --build build --target features
I see a lot of failed tests:The Calc example runs without errors:
✅ What did I expect to see?
Actually I don't know what exactly to expect. I find it akward that there are failed tests. So probably I should expect no failed tests?
📦 Which tool/library version am I using?
Docker Container with Debian 12.1 as you can see above I tried it on a Linux and Windows with WSL with the same outcome.
🔬 How could you reproduce it?
Create build directory
cmake -E make_directory build
Generate Makefiles
cmake -E chdir build cmake -DCUKE_ENABLE_EXAMPLES=on -DCMAKE_INSTALL_PREFIX=${prefix} ..
Build cucumber-cpp and tests
cmake --build build
Run unit tests
cmake --build build --target test
Run install
cmake --build build --target install
Check implementation against common cucumber test suite
cmake --build build --target features