Testing plan/document for testing of stand alone application software is required

[Mr_Engineer]

Hello,

I have deveopled a stand-alone application softwarw in LabIEW,  to perform data acquisition with 3rd party hardware. I want to perform software testing before its final delivery to user/customer.

What is standard document or standard plan or method or any document, to perform software testing?

Kind suggestions are required in this regard pls.

Regards

Jamal

[crossrulz]

Every company has their own templates and standards for these.  The general idea is to go through your requirements and make sure you test them.

If you really want help with this, I recommend looking up a local NI Alliance Partner who can help you through this.

[Mr_Engineer]

Thanks for reply.   Could please provide a sample test plan as a templete for reference .

Regards,

Jamal

[Norbert_B]

Jamal,

maybe you find it interesting if you'd search for IEEE documents on testing of software. Please note that there is quite some material available so you will have to take some time to implement your own version of a test specification.

Norbert

[Mr_Engineer]

Thanks, I have searched for IEEE testing templete. it's IEEE 829 standard for software testing.

But it's more general. I want something specific to LabVIEW to see how LabVIEW experts develop test plans for their application softwares built with LabVIEW.

Regards,

Jamal

[Norbert_B]

Jamal,

sadly, most applications (LV and other developement systems alike) are rather untested when leaving the developement machine for deployment. Most developers/companies don't care about testing when starting the project.

That being said, it is a good sign that you care about this topic.

IEEE gives good guidance on what you *should* do and what is *possible* in a reasonable effort. Still, it is the development team, ultimately the architect of the software who has to put up the test plan.

For most applications, these tests do have a focus like

- increased reliability (e.g. load tests)

- improved usability (e.g. end user beta test, "baby test")

- system runtime performance (e.g. speed benchmarks, load tests)

As crossrulz already pointed out: Each company has customized/custom-tailored testing needs and solutions (if they perform proper testing). If you don't have constraints on defining tests, i really recommend to stick as close as possible to IEEE, as this is possibly a door-opener for future projects. You have to notice that for specific environments, IEEE compliant testing is mandatory....

If you don't stick to it, make up your mind what you consider useful, ask friends and maybe you get some insights from other participants in this forum.

Norbert

[Mr_Engineer]

Thanks for reply.

1.  I want to be more specific so I'm interested in specific test plan if any one could provide.

I have developed an application software  with 64 bit LabVIEW 2013 full professional development system, I want to perform unit testing with LanVIEW unit test framework toolkit. But when I install unit test framework toolkit; a pop up manu is opened which shows that I must install 32 bit LabVIEW before installing unit test framework toolkit.

 2.  How I can resolve this issue?

Regards,

Jamal

[Norbert_B]

Jamal,

sadly, afaik, the UTF toolkit does not support 64-bit LV (see here).

Also please note that the UTF is used for basic module (unit) and for some integration testing. It is not designed to test a complete application.

That being said the UTF can greatly help in reducing test time itself. Still you have to create a test plan and implement appropriate test vectors for it.

Application test itself is not an easy topic, maybe you want to look for automatic test tools, e.g. test complete. Depending on the tool you have (or create), test specification might have to look slightly different.

The UTF for instance circumvents that by providing fields for "requirement IDs".

Norbert