We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the goal is to make sure that whenever we merge some PR during the refacto it does not affect the correct functionality of challengify in production
benefits of TDD :
integration test : challengify_ignore files are taken into account
integration test : delimiters are correctly handled per language
integration test : challenge file and directory structure gets generated at the correct location
integration test : file deletion is handled
integration test : challenge versions are generated at the correct location
integration test : file presence into a challenge version is handled correctly through challengify_iterate.yaml with to / for / from
integration test : ability to provide challenge version ranges for the presence of a file << specification needed
integration test : handle custom files like README_api.md across the challenge versions
README_api.md
integration test : handle presence of block of code according to only to / for / from version delimiters # ONLY_FROM_api_BEGIN
# ONLY_FROM_api_BEGIN
integration test : handle block of code challengification according to only to / for / from version delimiters # CHA_ONLY_FROM_api_BEGIN
# CHA_ONLY_FROM_api_BEGIN
The text was updated successfully, but these errors were encountered:
No branches or pull requests
the goal is to make sure that whenever we merge some PR during the refacto it does not affect the correct functionality of challengify in production
benefits of TDD :
challengify
integration test : challengify_ignore files are taken into account
integration test : delimiters are correctly handled per language
integration test : challenge file and directory structure gets generated at the correct location
integration test : file deletion is handled
challengify iterate
integration test : challenge versions are generated at the correct location
integration test : file presence into a challenge version is handled correctly through challengify_iterate.yaml with to / for / from
integration test : ability to provide challenge version ranges for the presence of a file << specification needed
integration test : handle custom files like
README_api.md
across the challenge versionsintegration test : handle presence of block of code according to only to / for / from version delimiters
# ONLY_FROM_api_BEGIN
integration test : handle block of code challengification according to only to / for / from version delimiters
# CHA_ONLY_FROM_api_BEGIN
The text was updated successfully, but these errors were encountered: