-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
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
Automated code testing using CI/CD #32
Comments
Yep, we should. |
@2G-Afroz How would you like to add the
Note We may temporarily make this repo c++ only, and further add other lang support as we go. |
we can include separate .txt file which will contain output of the code. |
What you meant by
Does that means that different example codes (written in different programming lang) of the same algorithm will have single output? |
Yes |
And we will mention that |
Elaborate this. |
I want to say that we will mention the |
Nope, that is not right. Different algo have different needs, like sorted/unsorted. So it is not right to be included in STANDARD. My idea
Benefits
|
There are actual codes in the repo (example codes). Those codes should be checked by the compiler and unit tests, so that there aren't any errors when we push any commit to the main branch.
So, I propose we use CI/CD for auto testing these programs for any errors.
The tests should perform:
The
compilation check
don't require any changes in the repo. But theTest case checks
needs:expected output
, then the test case fails.Majority of the program will have the input hardcoded (written in their source code), so only the
Expected output
is of concern.So, how should we provide the expected output in the repo.
I propose we include a output.txt file for each program
The text was updated successfully, but these errors were encountered: