Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added a test ensuring that new driver methods are added to the CoreDriver #456

Merged
merged 1 commit into from
Jan 20, 2014

Conversation

stof
Copy link
Member

@stof stof commented Jan 19, 2014

This test is written in a way ensuring that we get a nice failure and not a fatal error (the faster way to ensure the implementation of method would be to instantiate a child class of CoreDriver, but it would not be user-friendly).

I also moved the @throws UnsupportedDriverActionException to the interface as it is the right place to say that the exception should be thrown when the action is unsupported

@aik099
Copy link
Member

aik099 commented Jan 20, 2014

Great idea. With not only ensures high coverage, but also checks for human errors, that might have been forgotten to add new methods to CoreDriver or did it with wrong method signature.

stof added a commit that referenced this pull request Jan 20, 2014
Added a test ensuring that new driver methods are added to the CoreDriver
@stof stof merged commit ffd8593 into minkphp:develop Jan 20, 2014
@stof stof deleted the core_driver_completion branch January 20, 2014 08:23
@stof stof added this to the 1.6 milestone Mar 4, 2014
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants