Expand description
Automated UI testing client and protocol for Fission applications.
This crate provides the JSON protocol types (shared between the test client
and the desktop shell server) and a LiveTestClient that drives a running
Fission application over HTTP.
§Architecture
The application must be launched with FISSION_TEST_CONTROL_PORT=<port>.
The LiveTestClient connects to http://127.0.0.1:<port> and sends
TestCommand JSON payloads to /cmd, receiving TestResponse replies.
Re-exports§
pub use browser::detect_chrome;pub use browser::run_browser_smoke;pub use browser::BrowserSmokeMode;pub use browser::BrowserSmokeReport;pub use browser::BrowserTestOptions;
Modules§
Structs§
- Bounds
- A logical rectangle in test-space pixels.
- Live
Test Client - An HTTP client that drives a running Fission application for automated UI testing.
- Selector
Candidate - A candidate considered while resolving a selector.
- Selector
Failure - Detailed selector failure response.
- Selector
Query - A selector query with optional scoping and duplicate disambiguation.
- Semantic
Node - A node in the semantic accessibility tree, returned by
TestCommand::GetTree. Bounding rectangles are expressed in logical test-space pixels. - Text
Item - A visible text element with its bounding rectangle, in logical test-space
pixels, returned by
TestCommand::GetText.
Enums§
- Selector
- A high-level selector for resolving semantic nodes without manual coordinates.
- Selector
Failure Kind - Machine-readable selector failure category.
- Test
Command - A command sent from the test client to the running application.
- Test
Event - Events injected into the winit event loop via
EventLoopProxy. - Test
Response - The response from the application to a
TestCommand. - Visibility
State - How much of a semantic node is visible after viewport and clipping are applied.
Type Aliases§
- Test
Response Sender - Per-command response channel used by the shell event loop.