Looking for feedback on LabVIEW-based automated test workflows

[ansonyuu]

Hi all. I'm a new grad from the University of Waterloo trying to learn from practitioners who build or maintain LabVIEW/TestStand/PXI/DAQ/instrument-control test systems about what’s working and what’s painful in real deployments.

Not a sales pitch and not looking for troubleshooting help. I’d love to hear (even just a reply in-thread):

• Where does most time get burned? (debugging, flaky tests, maintainability, calibration, data review, reporting)

• How do you handle data logging + reporting today?

• If you need traceability/evidence (requirements/audits), what’s your current approach?

If you’re open to a brief 15-minute chat (voice or text) to go deeper, feel free to DM me.

Thanks in advance — even one sentence on your biggest headache is super helpful.

[Terry_ALE]

---

@ansonyuu wrote:

Hi all. I'm a new grad from the University of Waterloo trying to learn from practitioners who build or maintain LabVIEW/TestStand/PXI/DAQ/instrument-control test systems about what’s working and what’s painful in real deployments.

Not a sales pitch and not looking for troubleshooting help. I’d love to hear (even just a reply in-thread):

• Where does most time get burned? (debugging, flaky tests, maintainability, calibration, data review, reporting)

• How do you handle data logging + reporting today?

• If you need traceability/evidence (requirements/audits), what’s your current approach?

If you’re open to a brief 15-minute chat (voice or text) to go deeper, feel free to DM me.

Thanks in advance — even one sentence on your biggest headache is super helpful.

---

• Where does most time get burned? (debugging, flaky tests, maintainability, calibration, data review, reporting)

  • Poor planning where coding precedes thinking things through.  In these cases there is an 'attachment' to work that has been completed.  Developers do not wish to delete or rework code because of an associated value.
  • High coupling of features such as data acquisition and analysis code that may not need to take place when data is acquired.  Users and customers want 'one product' but this really adds complexity which is unnecessary.

• How do you handle data logging + reporting today?

  • I default to files which are binary which contain metadata structuring built in such as TDMS.  There are other formats which provide this such as .MAT.

• If you need traceability/evidence (requirements/audits), what’s your current approach?

  • Requirements Traceability Matrix