Rahix
(From #328) Back in the days, before `core::convert::Infallible` was added, we had `void::Void` to mark `Result`s which cannot ever produce the error variant. With it came the `void::ResultExt` extension trait...
While writing [`shared-bus`](https://github.com/Rahix/shared-bus) I was hit with the lack of a standardized Mutex type. `std` solves this by implementing the mutex type differently for all architectures it supports and this...
I've seen a shell send the following escape sequences which tbot doesn't handle well: ``` │ ├─(690600)< '\x1b7\x1b[r\x1b[999;999H\x1b[6n' ``` Individually, these mean: | Sequence | Meaning | | --- |...
The current verbosity levels do not provide much valuable control. I personally always have it set to `Verbosity.STDOUT` (= `-vv`) and I assume most other people have as well. Instead...
Currently, the CWD of a machine is largely undefined: For `SubprocessConnecter` it is going to be the CWD of tbot itself, for `SSHConnector` and similar, it is most likely `$HOME`....
Currently, when something goes wrong, tbot dumps a stack-trace and a tiny exception message. Even worse, often it is hard to decipher what actually went wrong and how to deal...
Global installation as it is currently described is convenient but bears problems when updating tbot: Newer tbot might not be 100% compatible with old projects. Instead, one could install tbot...
Currently, TBot will **always** turn the board off after running. For boards with a long boot cycle, this can considerably slow down test development. To allow quicker iterations, there should...
If kernel-logging is set to be verbose, kernel log-messages will clobber the serial console and lead to incorrect test results or prevent proper board initialization. tbot should at least be...
Roadmap
The current version is still pretty much what I drafted up initially. The design has shown a few flaws over time, which should be addressed in a new version. Here...