{{ message }}
Repository navigation
Test Suite - #22
Merged
Merged
Test Suite#22
Conversation
…to stop to depend on third party implementations due to our constraints of use the latest C++ features. Initially, we have: - Test Suite -> Common structure for handle related test cases - Test Case -> A particular user-defined code that will be the testing object - Test Results -> Structure for hold the results of different suites and the free test cases (There's still a very initial implementation, warnings are not handled by them) - Assertions -> Only implemented `assertEquals`. We are in a very initial state, so it's fine to test our development workflow right now Color features: Added some different colors to the terminal output, related by action. This should be completly refactored into their own feature, but due to the incoming std::print and std::format (that won't be usable until LLVM's 17 version, I don't know how to exactly proceed, because printing coloured strings could be done with the planned custom string implementation that we have planned, or just concatenating the color ANSI codes... hard to tell now. But we can think in such a feature in different ways
…the tracker. Declaring the suite library to the rest of the zork.conf(s)
…st suites now stores pointers to the targets, and we are able to avoid with this change the `arithmetic on a pointer to an incomplete type`, letting them on the top-level of the module. This will be useful when we split the components into their module partitions
…TestSuite and TestCase defined constructors
1. Assertions have now their own module 2. Deleted the default constructor for the test suites. A identifier must be generated always by the user
1. The suite results are now a member of the `Test Suite` type 2. More format and colours 3. Reorganized the Zork's configuration files
1. Generated a README.md for the `test-suite` 2. `assertNotEquals` standalone functions created
TheRustifyer
marked this pull request as ready for review
July 22, 2023 11:32
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Zero - test_suite - Very initial implementation of a own test suite, to stop to depend on third party implementations due to our constraints of use the latest C++ features.
The main reason behind this is due to the issues detected with
Clangversion >= 16 andCatch2, since it's imposible to buildCatch2with Clang. Instead of waiting them for fix this, we will implement our test suite from scratch.Initially, we have:
assertEqualsandassertNotEquals. We are in a very initial state, so it's fine to test our development workflow right nowColor features: Added some different colors to the terminal output, related by action. This should be completly refactored into their own feature, but due to the incoming std::print and std::format (that won't be usable until LLVM's 17 version, I don't know how to exactly proceed, because printing coloured strings could be done with the planned custom string implementation that we have planned, or just concatenating the color ANSI codes... hard to tell now. But we can think in such a feature in different ways
Update: Waiting for #23 to remove from the code the ANSI codes, since a formatter and a stylizer is ready to be merged to upstream.