QA/Execution/Web Testing/Continuous Build Integration: Difference between revisions
< QA | Execution | Web Testing
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Continuous Build Integration | ==Continuous Build Integration== | ||
'''The problem:''' | '''The problem:''' | ||
Currently, our Selenium tests (IDE, PHP) are run on-demand, manually, in isolation. Output of results.html is manually examined. | |||
'''What we'd like to see:''' | |||
A way of running *all* Selenium tests via a single (or few) button clicks (i.e. waterfall), and have the results automagically output in an easy-to-read format. | |||
'''Proposed solutions:''' | '''Proposed solutions:''' | ||
'''Current progress:''' | '''Current progress:''' | ||
Resources: | |||
[http://frazzleddad.blogspot.com/2009/02/getting-selenium-html-test-suites.html Automating IDE runs/reporting] | |||
Latest revision as of 18:33, 6 October 2009
Continuous Build Integration
The problem: Currently, our Selenium tests (IDE, PHP) are run on-demand, manually, in isolation. Output of results.html is manually examined.
What we'd like to see: A way of running *all* Selenium tests via a single (or few) button clicks (i.e. waterfall), and have the results automagically output in an easy-to-read format.
Proposed solutions:
Current progress:
Resources: