Friday, June 29, 2012

Feedback on WAAT

I am considering adding some functionality to WAAT. However, before I do that, I would like to know what your opinion is.

So, to all those who are either using, tried using, or, want to use WAAT: Can you please provide me some feedback based on the following questions:

  • Which flavor of WAAT do you use? 
    • Java
    • Ruby
    • Both
  • Have you faced any problems using WAAT? 
    • If yes, what problems? How did you resolve them?
  • WAAT using the httpSniffer approach has known limitations (namely: does not support https request capturing, and on non-Windows platform you need to run the tests using root access). 
    • Have you run into these limitations? 
    • How did you resolve the issue?
  • Do you find the WAAT wiki useful?
    • If not, what if done differently will provide more value?
  • Any other thoughts / comments on how WAAT can be made better?
Looking forward for your comments.



1 comment:

  1. (1) I am using Java
    (2) Since there are lots of methods which are internally calling each other, would be good to have kind of Javadoc, so that we know which method does what and if required we can tweak it as per our requirement
    (3) One issue which I faced was to fail the test case if 2 duplicate requests with matching taglist is found. The workaround I did was when actualSectionList was 2 and errorList.size() was 0, then to return null and then caught the null pointer exception and then failed the test case