Android LogCat log with keyword highlighting
These are some handy Linux terminal commands that give a filtered LogCat log. The given keywords are highlighted in the terminal The following command only shows prints from a given tag:
These are some handy Linux terminal commands that give a filtered LogCat log. The given keywords are highlighted in the terminal The following command only shows prints from a given tag:
This is my latest contraption. I made an AC power supply that can be controlled by the Yats test automatization software or any other tool that can send commands via a serial port. It provides 4 mains sockets that are controlled either through RS232 or manually using buttons. There is one isolated 220V and one… Read More »
I’m trying to finally get the Yats application to compile and run on both x86 and x64 Windows versions with a single build. The only library giving problems is System.Data.SQLite. I found an almost complete solution in stackoverflow. Here is a quick reminder on how to set up the Visual Studio project.
I have spent a few hours investigating where all the RAM has gone in my new Arduino project. I need to investigate newer versions (still running 1.0), I really hope there are improvements. My favorite WTFs: string constants are stored in RAM string constants can be stored in Flash. For that you need to wrap… Read More »
A Yats (Yet Another Test System) test scenario consists of test cases that may be contained in test groups. This creates a test tree structure. Each node (test case or test group) can be configured.
A Test Repository Manager is an interface between Yats framework and test case implementation. Currently only one Manager is implemented in order to support test cases written in C# (classes implementing IYatsTestCase interface). In the future, repository managers for shell scripts, NUnit test cases and other tests should be added. Multiple Repository Managers can be… Read More »
This is a list of .NET types supported by Yats as of today. More types and custom classes can be implemented (TODO: link to post on how to implement a new parameter type and editor)
All Yats test cases finish by returning one of the following results: NOT_RUN – set by Yats execution environment if the test case was skipped PASS / FAIL – returned by the test case itself INCONCLUSIVE – unexpected execution – the test case could not determine pass/fail or an exception was thrown during test case… Read More »