Skip to content

Commit c54c4cc

Browse files
[DOCUMENTATION] Apply changes as per Review (- WIP PR #228 -)
Changes in file .readthedocs.yaml: - fixed style regression - added more coments - added simple success testing Changes in file docs/FAQ.md: - added well placed punctuation. Changes in file tests/__init__.py: - added more to the docstrings.
1 parent 3f3f201 commit c54c4cc

File tree

3 files changed

+11
-4
lines changed

3 files changed

+11
-4
lines changed

.readthedocs.yaml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,8 @@ build:
3737
pre_build:
3838
# Build the project module that is to be documented ; continue even if build fails
3939
- make build || true
40-
# build the documentation ; avoid crashing even if docs fail
41-
- make -j1 build-docs || true
40+
# Build docs and verify output exists
41+
- make -j1 build-docs && test -d docs/www/_build/html
4242
post_build:
4343
# Move built documentation into place ; ignore if fails
4444
- cp -vfRp docs/www/_build/html/ "$READTHEDOCS_OUTPUT" || true
@@ -57,6 +57,7 @@ sphinx:
5757
#
5858
# Note:
5959
# - Enabling PDF output requires LaTeX installed in the build environment
60+
# - PDF output requires texlive-latex-recommended and texlive-fonts-recommended packages
61+
# - PDF builds may significantly increase build time and output size
6062
# - Ensure all documentation content is compatible with these formats
6163
# - Assess user demand for offline documentation before enabling
62-

docs/FAQ.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -228,7 +228,7 @@ work so far as this Multicast module is concerned.
228228
229229
### How do I build the documentation?
230230

231-
* Typically the documentation will be automatically built by CI/CD and posted to the official
231+
* Typically, the documentation will be automatically built by CI/CD and posted to the official
232232
documentation site.
233233

234234
* However if one still wishes to manually build the documentation, there is a make target for this:

tests/__init__.py

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,12 @@
2424
This package provides comprehensive testing coverage for various multicast functionalities
2525
including server operations, data processing, cleanup routines, and exception handling.
2626
27+
For specific test cases, see:
28+
- Server operations: test_hear_server.McastServerTestSuite
29+
- Data processing: test_hear_data_processing.RecvDataProcessingTestSuite
30+
- Cleanup routines: test_hear_cleanup.HearCleanupTestSuite
31+
- Exception handling: test_exceptions.ExceptionsTestSuite
32+
2733
Robust imports: These statements import the entire "multicast" module,
2834
allowing access to all its functionalities within the test environment.
2935
This may be flagged as an intentional cyclic import by pylint.

0 commit comments

Comments
 (0)