Talk:Capturing Messages: Difference between revisions

From STRIDE Wiki
Jump to navigation Jump to search
(New page: 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 St...)
 
No edit summary
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.'''
 
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.  
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.
RE: '''If your primary interest is in integration or QA-style testing, proceed to the Test Scripts topic.'''


Tim - lets discuss.
Tim - lets discuss.
Line 11: Line 10:


Comment on “Wiki - Getting Started”
Comment on “Wiki - Getting Started”
You will be using the FrameworkSetup.pl script to setup packages for a Windows Framework.  
'''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.
Perhaps should be “You will be using the FrameworkSetup.pl script to setup a Workspace with packages using a Windows Framework.



Revision as of 16: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” 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.

Comment on Instructions->Setup (here’s a real nitpickety item which I would probably ignore). The instructions say Run the following from a command line (cmd.exe). Then Navigate to the workspace location – which I took as from the command line as well, i.e. entering “cd c:\... Then Double click on the file CapturingMessages.ssw – which of course you can’t do from the command line.

Inconsistency/error in “Wiki – Performing the Exercise One way Command Message with Payload By Value - First bullet states “…with a payload passed by pointer and POOL memory usage.” - “… 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” 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 work empty may be misleading here. I think no payload is more accurate.

Inconsistency/error in “Wiki – Performing the Exercise” Broadcast Message with No Payload - First bulled states “…with a payload passed by value” – inconsistent with exercise title “No Payload”