Conversation
21c7f77 to
253cd95
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## 1.x #1940 +/- ##
==========================================
+ Coverage 79.67% 79.72% +0.05%
==========================================
Files 832 833 +1
Lines 24748 24771 +23
==========================================
+ Hits 19718 19749 +31
+ Misses 5030 5022 -8
🚀 New features to boost your workflow:
|
5dba5b6 to
5561f51
Compare
|
there is a bug in https://github.com/flow-php/flow/blob/1.x/phpunit.xml.dist#L75C1-L80C17 (those should have lib- prefix) which prevents types tests from being executed on the CI/CD 🤦♂️ I noticed because on my local machine I have overwritten phpunjt.xml.dist and noticed that html type related tests are failing |
|
(it was automatically closed since #1944 mentioned this as something that should be resolved) |
d56e6d4 to
ef8d7bf
Compare
|
I checked out locally to that branch (to figure out why infection is complaining) and when I execute: I'm getting: Which makes sense, that test is expecting that DOMDocument is going to wrap value with Different version of libxml perhaps? 🤔 |
|
As for CodeCove / Infection - this PR just does not have enough code coverage (I thought it's something else related to tools config). It adds some lines of code, but around 27% of HTMLEntry is not covered by any test |
Yes, here is the result of the investigation around this issue: |
norberttech
left a comment
There was a problem hiding this comment.
HTMLEntry needs better coverage
|
After taking another look at
public function test_construct_with_invalid_string_uuid_throws_exception() : void
{
$this->expectException(InvalidArgumentException::class);
new Uuid('invalid-uuid-string');
}
#[RequiresPhp('>= 8.4')]
public function test_create_with_proper_html_on_newer() : void
{
$html = '<html><body><div><span>bar</span></div></body></html>';
$document = new HTMLDocument($html);
self::assertSame($html, (string) $document);
}So what needs to happen is following:
Once values are extracted it should validate if given string is a valid HTML5 by checking if:
So now the test that is failing because of different versions of libxml should simply throw an exception. |
8764b22 to
937d7ed
Compare
254aacf to
d18f6af
Compare
Resolves: #1914
Change Log
Added
Fixed
Changed
Removed
Deprecated
Security