Comments (4)
I use the @internal
annotation to mark
that the associated Structural Elements are used purely for the internal workings of this piece of software.
In particular to avoid apearing such internal details in the API documentation.
I actually don't need those abstract methods in the trait. I have them there for convenience, so that the code makes sense while calling those methods from the expected PHPUnit API.
But for you as a PHPUnit user they are part of the public API of PHPUnit. Actually I don't know what should be a correct behaviour for this case. I don't think it's well defined in PHPDoc and last time I checked, this FIG soap was about to implode or at least PSR-5 died. Ok, before I make any action on that, I need some authoritative information about the correct behaviour. I'll try to get that from https://github.com/phpDocumentor/phpDocumentor2.
from php-mock-phpunit.
@malkusch Can you fully remove those abstract methods in the trait, as you said you don't need them actually? They add no value and just pollute inspections in PhpStorm.
from php-mock-phpunit.
@emirb Please see #27, methods from trait are there removed.
from php-mock-phpunit.
Thanks @webimpress!
from php-mock-phpunit.
Related Issues (20)
- PHPUnit 7 support HOT 3
- Searching new maintainer
- Compatibility with PHPUnit 7.4 HOT 5
- Not work if mocked in test method and tests was run from phpunit command HOT 1
- Add PHPUnit 8 support HOT 1
- Add PHPUnit 8.1 compatibility HOT 2
- Error: Call to undefined method phpmock\phpunit\MockObjectProxyNoReturnTypes::will() HOT 1
- Incompatibility with PHPUnit 8.4 HOT 2
- 'parameters' is private member, use getParameters() instead.
- Declaration of Codeception\Test\Test::toString() must be compatible with PHPUnit\Framework\SelfDescribing::toString(): HOT 3
- Declaration of phpmock\phpunit\MockDisablerPHPUnit6::endTest(PHPUnit\Framework\Test $test, $time) must be compatible with PHPUnit\Framework\BaseTestListener::endTest(PHPUnit\Framework\Test $test, float $time): void in /home/vagrant/Code/boursify-app/vendor/php-mock/php-mock-phpunit/classes/MockDisablerPHPUnit6.php on line 50 HOT 2
- phpunit 8.3: cannot implement PHPUnit\Framework\MockObject\Rule\InvocationOrder HOT 2
- phpspec/prophecy is now explicitely needed for tests HOT 1
- Incompatible declaration of MockDisablerPHPUnit6::endTest HOT 1
- InvocationOrder - it is not an interface HOT 1
- Support PHPUnit 10 HOT 2
- Mocking time function in one test method affects the other
- Incompatible with PHPUnit >= 10.3 HOT 7
- [QUESTION] - Deprecated Methods in phpunit 11 HOT 2
- Deprecation warnings HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from php-mock-phpunit.