-
Notifications
You must be signed in to change notification settings - Fork 409
test report formats
Sergey Bronnikov edited this page Feb 11, 2021
·
2 revisions
- TeamCity CI:
- DejaGnu
- HP QuickTest Professional
- IBM Rational Functional Tester
- Gallio Test Report
- Parasoft C/C++ test
- Ranorex
- TAPOUT - TAP Y J Specification
- Universal test output
- XML-based
- TestRail
- SonarQube
- GTester XML Format (convert to JUnit)
- Allure (XSD Schema)
- xUnit
- Microsoft Test (.TRX)
- YAML-based
- JSON-based
- MozLog
- Language Independent Test Format
- Chromium The JSON Test Results Format
- CMake
ctest
(also TAP13) - Go
go test
(JSON) - KernelCI JSON schema
- Common Reporter Interface (CRI) for JavaScript testing frameworks
Copyright © 2014-2025 Sergey Bronnikov. Follow me on Mastodon @[email protected] and Telegram.
Learning
- Glossary
- Books:
- Courses
- Learning Tools
- Bugs And Learned Lessons
- Cheatsheets
Tools / Services / Tests
- Code complexity
- Quality Assurance Tools
- Test Runners
- Testing-As-A-Service
- Conformance Test Suites
- Test Infrastructure
- Fault injection
- TTCN-3
- Continuous Integration
- Speedup your CI
- Performance
- Formal Specification
- Toy Projects
- Test Impact Analysis
- Formats
Functional testing
- Automated testing
- By type:
WIP sections
Community
Links