Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[SecurityBundle] Fix typo in the check_path validator #8782

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

Closed

Conversation

unkind
Copy link
Contributor

@unkind unkind commented Aug 18, 2013

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #3005, #2954
License MIT

Actually, validator of check_path value is broken by #3005. It doesn't throw any exception even if check_path is an URI.

I've faced with wrong tests class hierarchy: SecurityExtensionTest is abstract test and I have to create the same test configuration for every format: PHP, XML, YAML. It looks like we test Dependency Injection and Yaml components. Issue with check_path does not depend on format, but such class hierarchy leaves me no choice. And I can't put test case into ConfigurationTest, because it doesn't know anything about security factories.

It looks like it's better to create new class for SecurityExtension tests.

fabpot added a commit that referenced this pull request Aug 22, 2013
This PR was submitted for the master branch but it was merged into the 2.2 branch instead (closes #8782).

Discussion
----------

[SecurityBundle] Fix typo in the check_path validator

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #3005, #2954
| License       | MIT

Actually, validator of `check_path` value is broken by #3005. It doesn't throw any exception even if `check_path` is an URI.

I've faced with wrong tests class hierarchy: `SecurityExtensionTest` is abstract test and I have to create the same test configuration for every format: PHP, XML, YAML. It looks like we test `Dependency Injection` and `Yaml` components. Issue with `check_path` does not depend on format, but such class hierarchy leaves me no choice. And I can't put test case into `ConfigurationTest`, because it doesn't know anything about security factories.

It looks like it's better to create new class for `SecurityExtension` tests.

Commits
-------

155dca0 [SecurityBundle] Fix typo in the check_path validator
@fabpot fabpot closed this Aug 22, 2013
@unkind unkind deleted the security-bundle-check-path-bugfix branch August 23, 2013 20:01
fabpot added a commit that referenced this pull request Aug 28, 2013
This PR was squashed before being merged into the 2.2 branch (closes #8840).

Discussion
----------

[SecurityBundle] Move format-dependent tests from SecurityExtensionTest

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | —
| License       | MIT
| Doc PR        | —

This PR solves issue with tests in the SecurityBundle: current structure of tests force to repeat the same test case for every format (PHP, XML, YAML) even if it doesn't depend on them (see #8782).

Commits
-------

d463e25 [SecurityBundle] Move format-dependent tests from SecurityExtensionTest
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