Talk:Capturing Messages: Difference between revisions
No edit summary |
No edit summary |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Comments on “Wiki - Training Organization” | Comments on “Wiki - Training Organization” | ||
RE: '''STRIDE is applied to both xUnit-style and system-level testing.''' | RE: '''STRIDE is applied to both xUnit-style and system-level testing.''' | ||
| Line 12: | Line 12: | ||
RE: '''You will be using the FrameworkSetup.pl script to setup packages for a Windows Framework.''' <br> | RE: '''You will be using the FrameworkSetup.pl script to setup packages for a Windows Framework.''' <br> | ||
Perhaps should be “You will be using the FrameworkSetup.pl script to setup a Workspace with packages using a Windows Framework". | Perhaps should be “You will be using the FrameworkSetup.pl script to setup a Workspace with packages using a Windows Framework". | ||
<br> | <br> | ||
Inconsistency/error in “Wiki – Performing the Exercise | Inconsistency/error in “Wiki – Performing the Exercise"<br> | ||
RE: '''One way Command Message with Payload By Value''' | RE: '''One way Command Message with Payload By Value''' | ||
*First bullet states “…with a payload passed by pointer and POOL memory usage.” | *First bullet states “…with a payload passed by pointer and POOL memory usage.” – inconsistent with exercise title "By Value" | ||
*“… and a payload consisting of a long field.” It’s not clear to me whether you’re asking for a payload of type long, or a payload of type structure with a single field of type long. The use of the word field is a little confusing. | *“… and a payload consisting of a long field.” It’s not clear to me whether you’re asking for a payload of type long, or a payload of type structure with a single field of type long. The use of the word field is a little confusing. | ||
<br> | <br> | ||
Inconsistency/error in “Wiki – Performing the Exercise” | Inconsistency/error in “Wiki – Performing the Exercise”<br> | ||
RE: '''One way Response Message with Payload By Pointer''' | RE: '''One way Response Message with Payload By Pointer''' | ||
*First bullet states “…with a payload passed by value.” – inconsistent with exercise title “By Pointer” | *First bullet states “…with a payload passed by value.” – inconsistent with exercise title “By Pointer” | ||
*“…and a payload consisting of an int field.” Again, is this to be a payload of type int, or a structure with a single field of type int. | *“…and a payload consisting of an int field.” Again, is this to be a payload of type int, or a structure with a single field of type int. | ||
<br> | <br> | ||
Comment on “Wiki - Two Way Message with Response Payload” | Comment on “Wiki - Two Way Message with Response Payload”<br> | ||
RE: with an empty command payload | RE: '''with an empty command payload''' | ||
*Since we define a Stride message as having an optional payload, I think the | *Since we define a Stride message as having an optional payload, I think the word empty may be misleading here. I think '''''no''''' payload is more accurate. | ||
<br> | <br> | ||
Inconsistency/error in “Wiki – Performing the Exercise” | Inconsistency/error in “Wiki – Performing the Exercise”<br> | ||
RE: Broadcast Message with No Payload | RE: '''Broadcast Message with No Payload''' | ||
*First bulled states “…with a payload passed by value” – inconsistent with exercise title “No Payload” | *First bulled states “…with a payload passed by value” – inconsistent with exercise title “No Payload” | ||
<br> | |||
On first run, all tests failed due to incorrect message names used. Instruction was not explicit on what naming convention to use for the SMID definitions. | |||
<br> | |||
After changing SMID names, 3 tests passed, 1 (TWO_WAY_MSG) failed. | |||
<br> | |||
-- Try Again Incorrect instrumentation -- please try again (ID: 0cc2fe772eaf86fe53262099028b7ee2, BASIS: 2994ea239f033680c9df1db2d32e798e) | |||
Latest revision as of 17:46, 31 March 2008
Comments on “Wiki - Training Organization”
RE: STRIDE is applied to both xUnit-style and system-level testing. Was surprised to see this statement. We usually tell customers that Stride can be used for all types of testing up to (pre) system test.
RE: If your primary interest is in integration or QA-style testing, proceed to the Test Scripts topic.
Tim - lets discuss.
Comment on “Wiki - Getting Started”
RE: You will be using the FrameworkSetup.pl script to setup packages for a Windows Framework.
Perhaps should be “You will be using the FrameworkSetup.pl script to setup a Workspace with packages using a Windows Framework".
Inconsistency/error in “Wiki – Performing the Exercise"
RE: One way Command Message with Payload By Value
- First bullet states “…with a payload passed by pointer and POOL memory usage.” – inconsistent with exercise title "By Value"
- “… and a payload consisting of a long field.” It’s not clear to me whether you’re asking for a payload of type long, or a payload of type structure with a single field of type long. The use of the word field is a little confusing.
Inconsistency/error in “Wiki – Performing the Exercise”
RE: One way Response Message with Payload By Pointer
- First bullet states “…with a payload passed by value.” – inconsistent with exercise title “By Pointer”
- “…and a payload consisting of an int field.” Again, is this to be a payload of type int, or a structure with a single field of type int.
Comment on “Wiki - Two Way Message with Response Payload”
RE: with an empty command payload
- Since we define a Stride message as having an optional payload, I think the word empty may be misleading here. I think no payload is more accurate.
Inconsistency/error in “Wiki – Performing the Exercise”
RE: Broadcast Message with No Payload
- First bulled states “…with a payload passed by value” – inconsistent with exercise title “No Payload”
On first run, all tests failed due to incorrect message names used. Instruction was not explicit on what naming convention to use for the SMID definitions.
After changing SMID names, 3 tests passed, 1 (TWO_WAY_MSG) failed.
-- Try Again Incorrect instrumentation -- please try again (ID: 0cc2fe772eaf86fe53262099028b7ee2, BASIS: 2994ea239f033680c9df1db2d32e798e)