Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP Fully cover scripts/dewebsockify by tests #6083

Conversation

r-richardson
Copy link
Contributor

Make scripts/dewebsockify fully covered by tests.

Related Progress Ticket: https://progress.opensuse.org/issues/174232

WIP
Make scripts/dewebsockify fully covered by tests.

Related Progress Ticket: https://progress.opensuse.org/issues/174232
Copy link
Member

@okurz okurz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

err, I'm confused. https://progress.opensuse.org/issues/174232 is about os-autoinst, you add to openQA?

Comment on lines +120 to +125
subtest 'upgrade failure' => sub {
$t->tx($t->ua->start($t->ua->build_websocket_tx('ws://invalid')));
$t->status_is(101, 'Initial HTTP handshake for WebSocket returns a valid protocol switch');
$t->finished_ok(1006, 'WebSocket closed with status code 1006 (abnormal closure)');
$t->content_like(qr/Unable to upgrade to WebSocket connection/, 'Error message logged on WebSocket upgrade failure');
};
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test is about the websocket server of the web UI and has nothing to do with dewebsockify which the ticket is about.

Unless I'm overlooking something this tests also only tests the behavior of Mojolicious itself so that's on its own also not very useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants