| Conditions | 1 |
| Paths | 1 |
| Total Lines | 15 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
| 1 | <?php |
||
| 32 | public function testSimpleCacheTokenPersistence() |
||
| 33 | { |
||
| 34 | $simpleCache = new FilesystemCache(); |
||
| 35 | $tokenPersistence = new SimpleCacheTokenPersistence($simpleCache); |
||
| 36 | $token = new JwtToken('foo', new \DateTime('now')); |
||
| 37 | |||
| 38 | $tokenPersistence->saveToken($token); |
||
| 39 | |||
| 40 | $this->assertTrue($tokenPersistence->hasToken()); |
||
| 41 | $this->assertEquals($tokenPersistence->restoreToken()->getToken(), $token->getToken()); |
||
| 42 | |||
| 43 | $tokenPersistence->deleteToken(); |
||
| 44 | |||
| 45 | $this->assertFalse($tokenPersistence->hasToken()); |
||
| 46 | } |
||
| 47 | } |
||
| 48 |
PHP Analyzer performs a side-effects analysis of your code. A side-effect is basically anything that might be visible after the scope of the method is left.
Let’s take a look at an example:
If we look at the
getEmail()method, we can see that it has no side-effect. Whether you call this method or not, no future calls to other methods are affected by this. As such code as the following is useless:On the hand, if we look at the
setEmail(), this method _has_ side-effects. In the following case, we could not remove the method call: