User Tools

Site Tools


kb:bestpractices:testing:general

10 General Tips

Prepare before Testing

Do these during development to avoid pitfalls

  1. Stick to the Rules
  2. Conduct Code Reviews
  3. Static Code Analysis (VI Analyzer)

Miscellaneous

  • For conversions, test at least a few possible values!
    • technologies: flatten/unflatten, typecast, to/from variant…
    • actually execute the VI
    • not necessarily on target or FPGA, just in software
    • maybe generate random data
  • For any encoding / decoding, test both sides back-to-back
    • examples: protocols, recordings, anything transferred between systems…
    • actually execute the VIs by wiring them directly together
    • not necessarily on target or FPGA, just in software
    • maybe generate random data
    • Unit-Test!
  • Check for circular calling of functions (Requests, MHL cases, etc)
    • draw flow chart of actions to visualize potential problems
  • Check all configuration files on all systems
    • Deploy changes (or notify team members to do so)
    • Don't forget default .ini's in repo
  • Evaluate changes in context of full application
    • what happens around my piece of work?
    • is everything started/initialized etc for my change to work?
kb/bestpractices/testing/general.txt · Last modified: 2023/04/01 13:44 by joerg.hampel