tag:studios.thoughtworks.com,2008:/2008/5/9/automated-testing-poll/comments Mephisto Drax 2008-05-16T05:17:35Z Michel Sabourin tag:studios.thoughtworks.com,2008-05-09:1068:1074 2008-05-14T15:41:37Z 2008-05-14T15:41:37Z We're just starting to use FitNesse. We did not use any test automation tools before. We like the idea that customers (not developpers) be responsible for defining clearly upfront what contract systems must comply with. However simple FitNesse is meant to be, it still represents a non-negligible learning curve for non-IT personnel. This will more likely be our biggest challenge in implementing this tool. Adrian tag:studios.thoughtworks.com,2008-05-09:1068:1069 2008-05-10T14:17:25Z 2008-05-10T14:17:25Z <p>We use QTP for the most part for several reasons: <ul> <li>It's the corporate standard</li> <li>IE is our browser standard; many apps have not been written to work on Firefox and don't work there.</li> <li>Our QA team overall has historically not been geated to approach testing from anything more than a playback/record strategy. That has changed significantly in some areas, but not all.</li> <li>QA is not an area - particularly in difficult economic environments - in which we have traditionally invested.</li> </ul> <p>We use Selenium for smoke testing in our continuous integration environment. <p>Perhaps I'm not tuned in to the testing space, but in your list of TW technologies, I've only heard of Sahi beyond Selenium. What strategies are you using to gain visibility of these other testing platforms? <p>I'd love to explore using more advanced testing strategies and tools. It's just not an area where we are currently investing.