for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
namespace Btccom\JustEncrypt\Test;
use BitWasp\Buffertools\Buffer;
use BitWasp\Buffertools\BufferInterface;
use Btccom\JustEncrypt\EncryptionMnemonic;
class EncryptionMnemonicTest extends AbstractTestCase
{
/**
* @return array
*/
public function getConsistencyCheckVectors()
return array_map(function (array $row) {
return [Buffer::hex($row['data']), $row['mnemonic']];
}, $this->getTestVectors()['mnemonic']);
}
* @dataProvider getConsistencyCheckVectors
* @param BufferInterface $data
* @param $mnemonic
public function testConsistency(BufferInterface $data, $mnemonic)
$this->assertEquals($mnemonic, EncryptionMnemonic::encode($data));
$this->assertTrue($data->equals(EncryptionMnemonic::decode($mnemonic)));
\Btccom\JustEncrypt\Encr...onic::decode($mnemonic)
object<BitWasp\Buffertools\BufferInterface>
object<self>
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example:
function acceptsInteger($int) { } $x = '123'; // string "123" // Instead of acceptsInteger($x); // we recommend to use acceptsInteger((integer) $x);
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example: