Reset namespace for testing config docs
See original GitHub issueCurrently doctesting has been switched off for ScienceState
related docs, but ideally anything that suppose to work for the users should be tested. To make this happen we need to reset the namespace while testing, I’m certain there is a clever way to do it.
Bottom line, those docs should be tested by the time we ship it to the users, if nothing else by brute force removing the modules prior in a testsetup
directive, etc.
See discussion here: https://github.com/astropy/astropy/pull/8517#discussion_r289228267
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Troubleshooting | Config Connector Documentation
When a namespace's ConfigConnectorContext is deleted, Config Connector is disabled for that namespace, which prevents any remaining Config Connector resources ...
Read more >Customization - Codeception Docs
In this chapter we will explain how you can extend and customize the file structure and test execution routines. Namespaces. To avoid naming...
Read more >Best practices for writing unit tests - .NET - Microsoft Learn
Learn best practices for writing unit tests that drive code quality and resilience for .NET Core and .NET Standard projects.
Read more >Customize pipeline configuration - GitLab Docs
On the top bar, select Main menu > Projects and find your project. On the left sidebar, select Settings > CI/CD. Expand General...
Read more >Configuration | Grafana Loki documentation
Configuring Promtail Promtail is configured in a YAML file (usually referred to as config.yaml) which contains information on the Promtail server, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Assuming this still hasn’t been fixed, I have some ideas for this issue. I think we can take advantage of some more modern Python features (e.g. PEP-562) to clean up some of this mess.
@stargaser - I strongly feel that these should be sorted out before 4.0 as the current way I don’t see how well the behaviour is predictable in e.g. a pipeline, aka we should provide reproducible examples in the docs.