You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, Fossil Test only supports classic text-based output, which is clear but lacks interactivity and visual appeal. In scenarios with large test suites or tests that require real-time monitoring, a more dynamic and visually structured interface would improve usability and understanding. This limitation can make debugging or navigating test results more time-consuming.
Describe the solution you’d like
Introduce dual output modes to Fossil Test:
1. Text-Based Output (Default)
Retain the existing plain-text output for traditional use cases, such as CI/CD pipelines or simple terminal-based results.
2. TUI (Text User Interface) Mode
Add an interactive, curses-based TUI mode to visually represent test execution in real-time with enhanced clarity and functionality.
Command Proposal:
A new command-line flag could toggle between the two modes:
• --output=text (default)
• --output=tui
TUI Features:
1. Test Execution Summary Panel
• A live summary of total, passed, failed, and skipped tests.
• Highlighted in different colors:
• Green for passed tests.
• Red for failed tests.
• Yellow for skipped tests.
2. Real-Time Test Execution Log
• Display the name of the currently running test with a status indicator (e.g., Running, Passed, Failed).
• Update dynamically as the test suite executes.
3. Search and Filter Options
• Allow users to filter results based on status (passed, failed, skipped) or search for specific test names.
• Shortcut keys for navigation (n for next result, f for filter, etc.).
4. Detailed Test Output Section
• Select a test from the list to view its detailed output, including logs, errors, and stack traces.
• Keyboard navigation for scrolling through detailed logs.
5. Progress Bar
• A visual progress bar showing the overall execution progress, percentage completed, and estimated remaining time.
6. Keyboard Shortcuts (Example)
• q to quit TUI mode.
• f to filter by test result.
• p to pause/resume test execution (useful during live debugging).
7. Customizable Theme
• Options to switch between light and dark themes for better visual comfort.
Text-Based Output Enhancements:
1. Add optional verbosity levels (--verbose, --quiet).
• Verbose Mode: Detailed test execution logs.
• Quiet Mode: Minimal output, showing only the final summary.
2. Improve formatting with structured headers for different sections (e.g., summary, errors, logs).
3. Include visual symbols (e.g., checkmarks ✔, crosses ✘) alongside test statuses for a cleaner look.
Describe alternatives you’ve considered
• Using external TUI libraries to process and display Fossil Test outputs in a custom TUI, but this adds dependencies and is less convenient than native support.
• Relying on third-party test runners, though these often lack integration with Fossil Test’s unique features.
Additional context
A TUI would make Fossil Test more user-friendly, especially for developers running large test suites or needing live updates during debugging. The text-based output would still provide compatibility for pipelines and simpler use cases.
The text was updated successfully, but these errors were encountered:
dreamer-coding
changed the title
Feature Request: Dual Output Modes for Fossil Test – TUI and Classic Text-Based Output
Feature Request: Dual Output Mode for Fossil Test (Text-Based and TUI)
Jan 4, 2025
Is your feature request related to a problem? Please describe.
Currently, Fossil Test only supports classic text-based output, which is clear but lacks interactivity and visual appeal. In scenarios with large test suites or tests that require real-time monitoring, a more dynamic and visually structured interface would improve usability and understanding. This limitation can make debugging or navigating test results more time-consuming.
Describe the solution you’d like
Introduce dual output modes to Fossil Test:
1. Text-Based Output (Default)
Retain the existing plain-text output for traditional use cases, such as CI/CD pipelines or simple terminal-based results.
2. TUI (Text User Interface) Mode
Add an interactive, curses-based TUI mode to visually represent test execution in real-time with enhanced clarity and functionality.
Command Proposal:
A new command-line flag could toggle between the two modes:
• --output=text (default)
• --output=tui
TUI Features:
1. Test Execution Summary Panel
• A live summary of total, passed, failed, and skipped tests.
• Highlighted in different colors:
• Green for passed tests.
• Red for failed tests.
• Yellow for skipped tests.
2. Real-Time Test Execution Log
• Display the name of the currently running test with a status indicator (e.g., Running, Passed, Failed).
• Update dynamically as the test suite executes.
3. Search and Filter Options
• Allow users to filter results based on status (passed, failed, skipped) or search for specific test names.
• Shortcut keys for navigation (n for next result, f for filter, etc.).
4. Detailed Test Output Section
• Select a test from the list to view its detailed output, including logs, errors, and stack traces.
• Keyboard navigation for scrolling through detailed logs.
5. Progress Bar
• A visual progress bar showing the overall execution progress, percentage completed, and estimated remaining time.
6. Keyboard Shortcuts (Example)
• q to quit TUI mode.
• f to filter by test result.
• p to pause/resume test execution (useful during live debugging).
7. Customizable Theme
• Options to switch between light and dark themes for better visual comfort.
Text-Based Output Enhancements:
1. Add optional verbosity levels (--verbose, --quiet).
• Verbose Mode: Detailed test execution logs.
• Quiet Mode: Minimal output, showing only the final summary.
2. Improve formatting with structured headers for different sections (e.g., summary, errors, logs).
3. Include visual symbols (e.g., checkmarks ✔, crosses ✘) alongside test statuses for a cleaner look.
Describe alternatives you’ve considered
• Using external TUI libraries to process and display Fossil Test outputs in a custom TUI, but this adds dependencies and is less convenient than native support.
• Relying on third-party test runners, though these often lack integration with Fossil Test’s unique features.
Additional context
A TUI would make Fossil Test more user-friendly, especially for developers running large test suites or needing live updates during debugging. The text-based output would still provide compatibility for pipelines and simpler use cases.
The text was updated successfully, but these errors were encountered: