ruby.git/test/coverage/test_coverage.rb, branch v3_3_11

merge revision(s) 0d6263bd416338a339651fb97fe4d62701704c4b: [Backport #21220]

2025-05-17T06:21:08+00:00

	Fix coverage measurement for negative line numbers

	Fixes [Bug #21220]

	Co-Authored-By: Mike Bourgeous 
	Co-Authored-By: Jean Boussier

Fix method coverage comparisons

2023-10-16T00:48:05+00:00

Although Ruby's hashes preserve the insertion order, the ordering of
method coverage results is inherently nondeterministic, because they
are collected using `ObjectSpace`.

Revert "Don't reset line coverage for evaled code. (#8330)"

2023-09-04T10:52:08+00:00

This reverts commit 7e0f5df2f99693267d61636d23da47f79924e9d5.

https://bugs.ruby-lang.org/issues/19857#note-7

Don't reset line coverage for evaled code. (#8330)

2023-09-04T01:31:25+00:00

* Add failing test.

More coverage tests & specs. (#7171)

2023-01-22T00:49:13+00:00

* Add spec for eval and line coverage.

* Add test for main file coverage.

Test some missing coverage too. (#7041)

2023-01-18T22:59:51+00:00

Coverage.supported? recognizes oneshot_lines mode (#7040)

2022-12-29T08:23:25+00:00

This adds oneshot_lines as a mode of coverage that is supported.

Fix false LocalJumpError when branch coverage is enabled

2022-11-08T05:37:08+00:00

`throw TAG_BREAK` instruction makes a jump only if the continuation of
catch of TAG_BREAK exactly matches the instruction immediately following
the "send" instruction that is currently being executed. Otherwise, it
seems to determine break from proc-closure.

Branch coverage may insert some recording instructions after "send"
instruction, which broke the conditions for TAG_BREAK to work properly.

This change forces to set the continuation of catch of TAG_BREAK
immediately after "send" (or "invokesuper") instruction.

[Bug #18991]

Change a tab to spaces

2022-10-17T02:30:07+00:00

Add `Coverage.supported?` to detect what modes are supported.

2022-09-28T20:44:14+00:00