modularity-testing-framework

#15 Write documentation for project
Closed Opened by jscotka.

Closed
Reopen Issue

Improved inline code documentation
* Write documentation to source code to be able to use pydoc

Create uptodate docs for Framework
* Document inline config examples
* How to schedule tests
* Describe tools in tools directory
* Using PDC, taskotron, compose

Metadata Update from @jscotka:
- Issue tagged with: Prio0

Metadata Update from @jscotka:
- Issue assigned to jscotka

Can you please explain it a bit more this issue?
I think, this is upstream.

okay, I'll edit description.

Part of this issue done.
Initial pydoc documentation created.
documentation adapted to upstream version.

I will take this issue. From the issue description, I will need to:
- Document inline config examples
- Describe tools in tools directory
- Using PDC, taskotron, compose

It's somehow documented, but needs to be edited.

Metadata Update from @igulina:
- Issue assigned to igulina (was: jscotka)

Basically, @igulina did some it already. Let's create the new issues for rest stuff, which can arise in the future

Metadata Update from @phracek:
- Issue status updated to: Closed (was: Open)

@phracek , Those things mentioned in my previous comment are not done. I prefer to complete this card, not close it in 'partial' state and duplicate it by opening a new card.

Metadata Update from @igulina:
- Issue status updated to: Open (was: Closed)

Project moved to git hub.

Issues copied to:
https://github.com/fedora-modularity/meta-test-family/issues

Metadata Update from @jscotka:
- Issue status updated to: Closed (was: Open)
Metadata

Prio0

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.