Modular Data Acquisition
Distributed Measurement and Control
High-Performance Test
Automated Test System Development Software
Perspectives showcases how NI sees what’s next in the world of test and technology.
You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.
Provides support for NI data acquisition and signal conditioning devices.
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments.
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.
For the Validate Module\Validate DQMH Module (Headless).vi, consider formatting the Validation Results in xUnit format.
DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)HSE Discord Server (Discuss our free and commercial tools and services)DQMH® (Developer Experience that makes you smile )
After looking into the whole topic some more and discussing with other people, I do think that the DQMH Module Validation produces a code quality metric rather than a test metric.
Seeing as we use GitLab, I'd like to suggest for the validation tool to create reports in Code Climate syntax. See GitLab Code Quality - Implementing a custom tool for more details on that syntax.
For the record. You can glance at it --> https://felipekb.com/2020/09/28/vi-analyzer-and-gitlab-code-quality/
That's an implementation of links shared by Joerg.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
