Skip to content
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

Test policy topic added #135

Merged
merged 1 commit into from
Sep 7, 2023
Merged

Conversation

PeterTurcan
Copy link
Collaborator

Breaking the complex Testing section into smaller chunks. Adding this section as the test policy.

@cppalliance-bot
Copy link

An automated preview of the documentation is available at https://135.site-docs.prtest2.cppalliance.org/index.html

@@ -0,0 +1,53 @@
= Test Policy
:navtitle: Test Policy
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this term commonly used? I've never heard it before.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alandefreitas The term is used in the legacy intro. I could change it to "Test Procedures", or "Test Overview" or similar?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The term is used in the legacy intro

Oh OK.

I could change it to "Test Procedures", or "Test Overview" or similar?

It's up to you. "Test policy" might be good since it was already in the legacy intro. We can always change if someone complains.


* Use boost:test[] to create individual test cases and group them into test suites. Then use the library's test tools to verify the expected behavior.

* For simple cases, you can use `lightweight_test.hpp`, instead of boost:test[]. This header file is located in the `<boost-root>/boost/core` directory of your local installation.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't is easier to mention boost:core[]?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agreed, I'll reword this

Test Policy topic feedback
@cppalliance-bot
Copy link

An automated preview of the documentation is available at https://135.site-docs.prtest2.cppalliance.org/index.html

@PeterTurcan
Copy link
Collaborator Author

@alandefreitas thanks for the feedback, and squashed

@cppalliance-bot
Copy link

An automated preview of the documentation is available at https://135.site-docs.prtest2.cppalliance.org/index.html

@alandefreitas alandefreitas merged commit ccfb49d into boostorg:develop Sep 7, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants