Skip to content
This repository has been archived by the owner on Jun 6, 2018. It is now read-only.

Don't expect exception classes to be available on the top-level object #33

Closed
jarib opened this issue May 28, 2012 · 0 comments
Closed

Comments

@jarib
Copy link
Member

jarib commented May 28, 2012

The specs expect to be able to reference e.g. Watir::Exception::UnknownObjectException as just UnknownObjectException. This is done by including Watir::Exception in the top level object, and frequently leads to NameErrors that pop up in the real world but not in the specs.

We should either (a) fix the specs to reference the full exception name, or (b) only include the Exception module in the specs, not the top level object.

p0deje added a commit to watir/watir that referenced this issue Feb 18, 2015
@p0deje p0deje closed this as completed in 33249df Feb 18, 2015
p0deje added a commit to watir/watir that referenced this issue Feb 18, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant