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

Extended unit tests not discovered with command line runner. #968

Closed
aik099 opened this issue Jul 21, 2013 · 2 comments
Closed

Extended unit tests not discovered with command line runner. #968

aik099 opened this issue Jul 21, 2013 · 2 comments

Comments

@aik099
Copy link

aik099 commented Jul 21, 2013

I have following directory structure:

tests
tests\RepkaQA\HtmlElements\TypifiedElementProxyTest.php
tests\RepkaQA\PageObject\WebElementProxyTest.php

File contents:

<?php

class TypifiedElementProxyTest extends WebElementProxyTest { ... }

and

<?php

class WebElementProxyTest extends \PHPUnit_Framework_TestCase { ... }

When I run phpunit it picks up phpunit.xml with following content:

<testsuites>
    <testsuite name="PageObject">
        <directory>tests/RepkaQA/PageObject</directory>
    </testsuite>
    <testsuite name="HtmlElements">
        <directory>tests/RepkaQA/HtmlElements</directory>
        <exclude>tests/RepkaQA/HtmlElementsLive</exclude>
    </testsuite>
</testsuites>

and runs both tests.

However if I run phpunit tests it doesn't run tests\RepkaQA\PageObject\WebElementProxyTest.php test. I can say for 100% that it doesn't run any test case, that was used as super class for other test case.

However maybe the problem is in the order of test case location in folder, where extended test case is located first and it's super class is somehow marked as processed.

@whatthejeff
Copy link
Contributor

Thanks for the bug report, @aik099. I think this may be a dupe of #529. If it's not, please let me know and I'll re-open the ticket.

@aik099
Copy link
Author

aik099 commented Jul 21, 2013

Yes, this was the right issue, thanks. However I'm wondering if anybody is planning on fixing it after 1 year.

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

No branches or pull requests

2 participants