...
Attendees: Michael Berger, Ed Orsini, Don Flanders
Funcunit does not meet initial requirements because it does not work in current versions of Firefox. It was a front end to Selenium, so we need not test it if we continue to test Selenium.
Seventh Meeting 10/3/2011
Attendees: Michael Berger, Ed Orsini, Don Flanders, Sean Velury, Felicia Leung, Judith McJohn, Alex Kozlov
After a hiatus while everyone delivered early fall work, we got back together. Current status is we are down to two products, Selenium and Appperfect. We are in process of testing the Selenium back end, and having everyone test the Selenium IDE front end (which some of us have used successfully). In addition, at our next meeting Ed Orsini will demo Appperfect so we can see what further testing we should do with it.
Eighth Meeting 10/18/2011
Attendees: Michael Berger, Ed Orsini, Don Flanders, Sean Velury, Felicia Leung, Judith McJohn
Ed showed us Appperfect. It was not perfect: he had problems with html selects (dropdowns). He has requested help from them, and is trying to get a complete end to end test.
We looked more at Selenium. We are close to get an end to end run through our test application, but so far we have not added all the assertions we need to make it a real "test."
We have split into several groups: Felicia, Judith and Sean are trying to finish up the test. Mike is trying to get Selenium running on his Mac and in a Linux VM. Then we will run the finished test in all combinations of OS/browser that we support. Meanwhile Ed continues to work on Appperfect.
We hope to have one or two more meetings and then write a report.
Ninth Meeting 11/14/2011
Assessed the results so far:
1. Jude likes Selenium, but thinks it is not be all end all, not that easy to set up and debug
2. Lisa defers to developers, thinks Help Desk can learn to run tests.
3. Felicia not as easy to make the test work, hard to figure out why, some of the selectors are not that good, drawback of the tool is the amount of checking,
4. Sean says he uses record and playback to get DOM ids, then hand codes his test. Points to a weakness in our test of Selenium, we did not test the coding process.
Hardware requirements: need to be able to get to the all the OS/brower combos
1. Need someone who is the product evangelist, creates the docs, builds some baseline tests, shows handle problem items (type versus type keys), trains developers and help desk
2. Need dedicated hardware/software and test users (Touchstone and certificates)
3. Need someone to coordinate and maintain the environment
4. Management buyin and continued support
5. A project and a project plan and project manager
6. Need to do the following testing of Selenium: Need to get Safari working on the Mac, need to test Selenium server on Linux. Need to test on Lion.