feat: update OSPS-QA-06

[Satarupa22-SD]

Refer #546

[evankanderson]

I'd like a little more justification for splitting this; I feel like documenting the various environments and methods for running the tests as a single control is not unreasonable; this could be phrased without "and" as:

The project documentation MUST clearly document all supported test environments, including invocation instructions.

[funnelfiasco]

I agree with Evan's suggestion. What we really want is for projects to document tests. "How" and "when" are elements of that documentation and don't require separate controls. This is another case of "state the outcome in the text and provide more details in the description"

[Satarupa22-SD]

The project documentation MUST clearly document all supported test environments, including how tests are invoked, manually or by automated triggers.

Instead of splitting it into two separate requirements can we use the above. CC: @funnelfiasco @evankanderson @eddie-knight

[evankanderson]

The project documentation MUST clearly document all supported test environments, including how tests are invoked, manually or by automated triggers.

Instead of splitting it into two separate requirements can we use the above. CC: @funnelfiasco @evankanderson @eddie-knight

, manually or by automated triggers feels like a bit of a comma-splice. Maybe , _whether_ manually or by automated triggers?

[Satarupa22-SD]

@evankanderson I have updated this as per the changes you proposed.