Developer Tools
The documentation of each developer tool can also be found in the tool
directory in the NOTES.md file.
- Overview
asdfassertionscode_metricsdead_code_scannerdebug_messagesdebuggerdiagramsdoclethelpissue_creatorlgtdoclgtunit- Main files
- API documentation
- Loading
- Testing
- Writing and running tests
- Automating running tests
- Parametric test objects
- Test dialects
- User-defined test dialects
- QuickCheck
- Skipping tests
- Checking test goal results
- Testing local predicates
- Testing non-deterministic predicates
- Testing generators
- Testing input/output predicates
- Suppressing tested predicates output
- Tests with timeout limits
- Setup and cleanup goals
- Test annotations
- Working with test data files
- Flaky tests
- Debugging messages in tests
- Debugging failed tests
- Code coverage
- Utility predicates
- Exporting test results in xUnit XML format
- Exporting test results in the TAP output format
- Generating Allure reports
- Exporting code coverage results in XML format
- Automatically creating bug reports at issue trackers
- Minimizing test results output
- Known issues
lintermakepacks- Requirements
- API documentation
- Loading
- Testing
- Usage
- Registries and packs storage
- Virtual environments
- Registry specification
- Registry handling
- Registry development
- Pack specification
- Pack URLs and Single Sign-On
- Multiple pack versions
- Pack dependencies
- Pack portability
- Pack development
- Pack handling
- Pack documentation
- Pinning registries and packs
- Testing packs
- Security considerations
- Best practices
- Installing Prolog packs
- Known issues
ports_profilerprofilertutorwrapper