Add Functional Verification Test Plan to Wiki

[Snell1224]

I would like to add the following Functional Test Plan to the ldms-test wiki page.

They are currently located under my forked branch of ldms-test.

Functional Verification Test Plan: Test plan for all plugins associated with the software samplers, storages, transports, etc. across various platforms.

• https://github.com/Snell1224/ldms-test/wiki/Functional-Verification-Test-Plan

Configuration Options: Contains the option combinations for the sampler, store and authentication configurations. Used by the Functional Verification Test Plan.

• https://github.com/Snell1224/ldms-test/wiki/Configuration-Options

Please let me know if any changes need to be made.

[tom95858]

@Snell1224 thanks for doing this. What is missing here are the requirements and the verification. For example, you enumerated all of the options for each sampler, but didn't say what that option was supposed to do (requirement), and how it was to be tested (verification).

[Snell1224]

@tom95858 Okay I will add the requirements, thank you for letting me know.

For verification - I thought this was covered with the "Tested by" column for the sampler table in the Functional Verification Test Plan (i.e. MC- make check/make installcheck; LT- ldms-test, etc.). Do I also need to include the test case details/procedure for each sampler option?

[tom95858]

That just names the test case, it doesn't say what is being verified and how. IOW how does the test case verify the functional requirement.

[Snell1224]

@tom95858 Okay. Before changing all of the tables - Could you please review the two sampler tables with these changes (i.e. app_sampler & appinfo) and let me know if this is what you expect or if there is anything else that needs to be changed/added?

Updated tables: https://github.com/Snell1224/ldms-test/wiki/Configuration-Options-With-Req.-and-Verif.
Thanks!

[tom95858]

I don't think the results belong in the test plan. That is a separate document. What is your intention regarding the contents of the 'assertion' column?

…

On Wed, Dec 15, 2021 at 2:28 PM Sara W ***@***.***> wrote: @tom95858 <https://github.com/tom95858> Okay. Before changing all of the tables - Could you please review the two sampler tables with these changes (i.e. app_sampler & appinfo) and let me know if this is what you expect or if there is anything else that needs to be changed/added? Updated tables: https://github.com/Snell1224/ldms-test/wiki/Configuration-Options---With-Req.-and-Verif . Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABVTPXFAXOGWENYLR4TDXZ3URECAJANCNFSM5J2ANOUQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Thomas Tucker, President, Open Grid Computing, Inc.

[Snell1224]

@tom95858 I plan to use the assertion column for identifying which assertion number in the test case was used to test the sampler option (i.e. for the app_sampler, assertion#1 tests that data is being sent to the daemon with the set "stream_name").....If the assertion is considered the 'results' then I can remove this column from all tables in the Test Plan.