From: "Kenny Smith" <[EMAIL PROTECTED]> > I looked over the ProtocolSimulator and I have some questions. What is > it primarily used for? For example, is it used for stress testing or > functional testing (or both?)
It was for RFC compliance and simulating specific client interactions. Repetions and stress test arguments were added to make it easier to crank up the load and expose problems that may be stess related. The idea was - Get script input from RFC or snoop on traffic, say using tcpdump-ethereal. - Generalize and code validation using PERL REGEX. Most of the validation may be check for response code and test for protocol compliance. - Make it easy to add a large number of validation in a tester friendly manner. Basically one could read RFC, generate assertions and document assertions as protcol simultion. This would give valid and coded testcases without any need to write code. > I'm personally inclined to just write junit tests that excersize the > different SMTP command sequences, but I'm interested to know what > thought processes and whatnot have already gone on that has shown that > approach to be lacking. This is a good approach. I just found it more work. Wrote the SMTPTest in JUnit that is checked in and the smtp protocol simulation test. I have been trying to find the most elegant and low cost approach to testing and have been going to and fro. Try things out yourself, and see what works best for you. Junit is a good safe choice. Harmeet -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
