Click here to Skip to main content
15,893,622 members

Stephan Meyn - Professional Profile



Summary

    Blog RSS
9,331
Author
80
Authority
68
Debator
20
Editor
2
Enquirer
25
Organiser
155
Participant
I am a Software Engineer/Consultant. My work is focussed on helping teams to get more out of their work. So I teach how to do requirements, analysis and design in a format that is easy to understand and apply.
I help with testing too, from starting developers on automated unit testing to running whole testing teams and how they cooperate with development.

For really big projects I provide complete methodologies that support all of the lifecycle.

For relaxation I paddle a sea kayak around Sydney and the Central Coast or write utilities on rainy days to make my life easier.

Groups

Below is the list of groups in which the member is participating

To connect Business to the IT services effectively you must define the processes where both sides interact:

Requirements
Project Governance
Testing & Acceptance
Methods Consulting offers comprehensive high value services to address issues in effective IT Service Delivery.

This is a Organisation
This member has Administrator, Manager, Author, Member status in this group

1 members

Reputation

Weekly Data. Recent events may not appear immediately. For information on Reputation please see the FAQ.

Privileges

Members need to achieve at least one of the given member levels in the given reputation categories in order to perform a given action. For example, to store personal files in your account area you will need to achieve Platinum level in either the Author or Authority category. The "If Owner" column means that owners of an item automatically have the privilege. The member types column lists member types who gain the privilege regardless of their reputation level.

ActionAuthorAuthorityDebatorEditorEnquirerOrganiserParticipantIf OwnerMember Types
Have no restrictions on voting frequencysilversilversilversilver
Bypass spam checks when posting contentsilversilversilversilversilversilvergoldSubEditor, Mentor, Protector, Editor
Store personal files in your account areaplatinumplatinumSubEditor, Editor
Have live hyperlinks in your profilebronzebronzebronzebronzebronzebronzesilverSubEditor, Protector, Editor
Have the ability to include a biography in your profilebronzebronzebronzebronzebronzebronzesilverSubEditor, Protector, Editor
Edit a Question in Q&AsilversilversilversilverYesSubEditor, Protector, Editor
Edit an Answer in Q&AsilversilversilversilverYesSubEditor, Protector, Editor
Delete a Question in Q&AYesSubEditor, Protector, Editor
Delete an Answer in Q&AYesSubEditor, Protector, Editor
Report an ArticlesilversilversilversilverSubEditor, Mentor, Protector, Editor
Approve/Disapprove a pending ArticlegoldgoldgoldgoldSubEditor, Mentor, Protector, Editor
Edit other members' articlesSubEditor, Protector, Editor
Create an article without requiring moderationplatinumSubEditor, Mentor, Protector, Editor
Approve/Disapprove a pending QuestionProtector
Approve/Disapprove a pending AnswerProtector
Report a forum messagesilversilverbronzeProtector, Editor
Approve/Disapprove a pending Forum MessageProtector
Have the ability to send direct emails to members in the forumsProtector
Create a new tagsilversilversilversilver
Modify a tagsilversilversilversilver

Actions with a green tick can be performed by this member.


 
GeneralUnit Testing Pin
Stephan Meyn30-Oct-04 13:53
Stephan Meyn30-Oct-04 13:53 
I have been having a discussion with Marc Clifton in regards to unit testing.
Marc has been confirming what I have been suspecting. Writing good unit test cases is hard. It is easy to write a positive test case that verifies that the application does the right thing if it is given expected conditions. But trying to find a negative test case that is likely to break the component it is much harder.

So while we have great tools, techniques and processes at hand, we have managed to address everything but the hard bit.

Compare this with system testing. System testers have the same problem yet they do come up with reasonable negative test cases.
I am speculating that it has to do with the specifications that are available. A system tester has (hopefully) Use Cases, which are narratives. The strength of narratives are that they can contain nuances and ambiguity that leads the reader to find potential weaknesses.
On the other hand the designer of a component has non-narrative style specifications: class diagrams, interfaces, sequence diagrams, state diagrams (in order of commonality). These are clear and concise pieces of instruction to the designer. And that may be the problem. They are so deterministic that they do not invite the reader to think of what might go wrong.

More about this later

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.