Test Coverage for No Local PTY and Remote PTY #991
Assignees
Comments
|
Closing this in favor of #975 |
hatched
pushed a commit
to hatched/teleport-merge
that referenced
this issue
Nov 30, 2022
…l#991) * display audit log events with UTC time * added UTC to column headers on recordings and audit log * prettier * moved utc creation to api response * move timezone offset to display time function * removed unused imports * display date string only
hatched
pushed a commit
that referenced
this issue
Dec 20, 2022
* display audit log events with UTC time * added UTC to column headers on recordings and audit log * prettier * moved utc creation to api response * move timezone offset to display time function * removed unused imports * display date string only
hatched
pushed a commit
that referenced
this issue
Feb 1, 2023
* display audit log events with UTC time * added UTC to column headers on recordings and audit log * prettier * moved utc creation to api response * move timezone offset to display time function * removed unused imports * display date string only
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue
Teleport needs test coverage of how the server should behave when you have no local PTY but have a remote PTY.
We essentially want to test something like this:
Where the expected output is
1\r\n2\r\n\nbut the test for this was flakey either because of a bug in the PTY library we are using or elsewhere. We need to hunt this down and re-add a test for this.The text was updated successfully, but these errors were encountered: