Hi Angelo, > definately a good addition, I tested only services now, I gave up the > PageTester, it's not practical to use it, and yet to learn that Integrated > test, I have been looking for a way to test pages and components, will give > your Testify, hope it will not be like PageTester:)
That's exactly why I wrote Testify. PageTester is good but it's slow to create one (I was finding about 4secs for the first instances and about 2secs for each other instance) and I was finding I needed different instances for different tests - so my tests were taking ages to run. Also it was very difficult to use mocks in the tests. So Testify takes advantage of all the good infrastructure in PageTester but makes it very fast because you can share one TapestryTester (which is just a subclass of PageTester) amongst all your tests - so you just get a one-off startup cost and then all the other tests are free. I also added in facilities to make using Mocks very simple and that plus the speed means it's practical to do lots of small-scale tests in the TDD style. Hopefully you'll find it's just what you were looking for :-) And if not, let me know the problem and I'll try to fix it. Paul ------------------ Paul Field Research IT Deutsche Bank --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
