CLD-R Testing Section

[Kenny_K]

I was looking through the CLD-R practice exams, and there is a section on Testing.

It includes Functional, Performance, Stress, Usability, Regression Configuration, Integration and Error.

Does anyone know where I can find out what NI defines each of these tests?  I cant find it anywhere on the site or in the Help section.  I must be typing in something incorrectly.

Thanks.

[AdnanZ]

These are found in the LabVIEW courses manuals. I am not sure which ones but it's in one of the LabVIEW specific courses. A general understanding of these concepts through wikipedia should be enough for the exam I would think.

[KHartley]

Kenny,

Please email certification@ni.com for any questions you may have about the test. They will be able to assist you.

[immercd1]

I have this same question.  Was this ever resolved?  I can't find all of these definitions in wikipedia.org, and are we sure that the definitions match?

Thanks.

[C-Dav]

Immercd1,

My best suggestion would be the same as Kyle's, above: get in touch with certification@ni.com for these details.

Regards.

[GPeople]

I know this is an old thread but I am having same problem while trying to study for my CLD-R.

Question 29. What method of testing is shown in the figure below?

1. Functional Testing

2. Integration Testing

3. Configuration Testing

4. Performance Testing

The diagram for question 29 could very well be testing the configuration of the VI shown which is NOT the correct answer,  just another TRICK question.

[GPeople]

Ha...found this when looking for something completely different!

http://zone.ni.com/reference/en-XX/help/371361N-01/lvdevconcepts/testing_guidelines/

[SergioR]

I was also searching for this topic... here is what I have gathered:

• Functional testing: Validates that the software meets the functional requirements. Pass an input to the VI and compare its output with the expected values.
• Performance testing: Validate that the program meets minimum performance requirements, such as execution time, memory usage, etc.
• Stress testing: Validate the program outside its design limits to find where unexpected failures may occur.
• Usability testing: Evaluate the user-friendliness of the program, involving end user access to the application to obtain useful feedback.
• Regression testing: Tests the application whenever new features are added to ensure existing features are not impacted.
• Configuration testing: Validate the system in different software configurations, such as different hardware, screen resolutions, operating systems, etc.
• Reliability testing: Verify that the application functions in a non-development environment. It involves alpha and beta testing.
• Integration testing: Tests code modules within the system as a whole, as they are developed. In top-down integration testing, test the high-level VIs first and move down the hierarchy. In bottom-up integration testing, test the low-level VIs first and move up the hierarchy. Top-down requires creating stub VIs to fill in for VIs that are not developed. Bottom-up requires creating test VIs to call the low-level VIs.