You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 22, 2025. It is now read-only.
jarib edited this page Aug 14, 2010
·
22 revisions
Why doesn’t Celerity recognize elements identified with non-ASCII characters?
Celerity encodes all strings as UTF-8, so you should save your test scripts as UTF-8 as well.
To make Watir use UTF-8, add this line to your test suite: WIN32OLE.codepage = WIN32OLE::CP_UTF8. (WTR-219)
Can I watch my tests execute?
Celerity uses HtmlUnit, a headless Java browser library, to interact with web pages. This makes it a lot faster than driving
a real browser at the cost of not having any visual feedback from your tests. To work around this you can use one of apps from the CelerityViewers repo to simulate driving a browser. Celerity won’t actually drive these, but sends them an HTML string for rendering over DRb on every page load.