mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-08-09 01:29:17 +00:00
LibTest: Support death tests without child process cloning
A challenge for getting LibTest working on Windows has always been CrashTest. It implements death tests similar to Google Test where a child process is cloned to invoke the expression that should abort/terminate the program. Then the exit code of the child is used by the parent test process to verify if the application correctly aborted/terminated due to invoking the expression. The problem was that finding an equivalent way to port Crash::run() to Windows was not looking very likely as publicly exposed Win32/ Native APIs have no equivalent to fork(); however, Windows actually does have native support for process cloning via undocumented NT APIs that clever people reverse engineered and published, see `NtCreateUserProcess()`. All that being said, this `EXPECT_DEATH()` implementation avoids needing to use a child process in general, allowing us to remove CrashTest in favour of a single cross-platform solution for death tests.
This commit is contained in:
parent
dc707e6ed8
commit
744fd91d0b
Notes:
github-actions[bot]
2025-05-16 19:24:44 +00:00
Author: https://github.com/ayeteadoe
Commit: 744fd91d0b
Pull-request: https://github.com/LadybirdBrowser/ladybird/pull/4698
Reviewed-by: https://github.com/ADKaster ✅
Reviewed-by: https://github.com/AtkinsSJ
Reviewed-by: https://github.com/R-Goc
13 changed files with 133 additions and 101 deletions
|
@ -9,7 +9,7 @@
|
|||
|
||||
TEST_CASE(char_data_ending)
|
||||
{
|
||||
EXPECT_NO_CRASH("parsing character data ending by itself should not crash", [] {
|
||||
EXPECT_NO_DEATH("parsing character data ending by itself should not crash", [] {
|
||||
// After seeing `<C>`, the parser will start parsing the content of the element. The content parser will then parse any character data it sees.
|
||||
// The character parser would see the first two `]]` and consume them. Then, it would see the `>` and set the state machine to say we have seen this,
|
||||
// but it did _not_ consume it and would instead tell GenericLexer that it should stop consuming characters. Therefore, we only consumed 2 characters.
|
||||
|
@ -17,17 +17,15 @@ TEST_CASE(char_data_ending)
|
|||
// input when we only have 2 characters, causing an assertion failure as we are asking to take off more characters than there really is.
|
||||
XML::Parser parser("<C>]]>"sv);
|
||||
(void)parser.parse();
|
||||
return Test::Crash::Failure::DidNotCrash;
|
||||
});
|
||||
}());
|
||||
}
|
||||
|
||||
TEST_CASE(character_reference_integer_overflow)
|
||||
{
|
||||
EXPECT_NO_CRASH("parsing character references that do not fit in 32 bits should not crash", [] {
|
||||
EXPECT_NO_DEATH("parsing character references that do not fit in 32 bits should not crash", [] {
|
||||
XML::Parser parser("<G>�"sv);
|
||||
(void)parser.parse();
|
||||
return Test::Crash::Failure::DidNotCrash;
|
||||
});
|
||||
}());
|
||||
}
|
||||
|
||||
TEST_CASE(predefined_character_reference)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue