An updated version of Yats is available in the Downloads section. The main changes: A major refactoring of logging code. Clean interfaces were defined and implemented, previous workarounds removed; Source solution upgrade – now compatible with the free Visual Studio 2013 Community edition! Created solution folders, finally started to use NuGet; Bug fixes What’s next?… Read More »
Yats now supports composite test cases. A selected test sequence or part of it can be exported to a test case file: Be sure to save the file in a directory set up to contain test cases: The test case shows up in the Test Case window. Now it can be added to other test… Read More »
This should help you to get started writing a Yats test case. We will create a Visual Studio solution, set up project dependencies and debug a very simple test case. We are assuming that Yats is installed at C:\Program Files\Yats Create a new C# DLL project: Add the following DLL dependencies to the project: attributes.dll,… Read More »
A summary of serial commands for the Velleman PS3005D lab power supply:
This post will give an example on how to add support for a custom test parameter type. The basic idea of test parameter value handling could be summarized as such: A parameter of a certain type is declared in a test case. In this example, the test case parameter could look like:
I’ve just discovered an undocumented command of the Velleman PS3005D programmable lab power supply. This PSU is available as a number of clones like Korad KA3005P reviewed at EEVBlog. I don’t know much about the serial communication protocol in the other PSU variants, perhaps they are different.
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.
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.