Add test for 'throttle-ui-updates' config
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/1250)
In GitLab by [[Gitlab user @tpollard]](https://gitlab.com/tpollard) on Jan 15, 2020, 12:48
## Background
With https://gitlab.com/BuildStream/buildstream/merge_requests/1745 landing, it would probably be beneficial to add tests to check the non restricted behaviour & also ensuring the default tick driven UI is functional. This could potentially harness something along the lines of the pexpect fixtures we already have, parsing the inflight session pager although input interactivity isn't actually needed. Something as simple as checking the status area would probably suffice.
----
[//]: # (To review information about possible relevant labels for this issue please view the list of labels: https://gitlab.com/BuildStream/buildstream/labels)
Contributor guide
Research direction
Locate the existing pexpect fixtures and the code handling the `throttle-ui-updates` configuration, then review how the inflight session pager exposes its status area. Run the relevant existing UI tests and add coverage for unrestricted behavior and the default tick-driven UI, with the status area providing the observable completion check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100