Skip to content

[Merged by Bors] - Remove duplicate asserts in test#5648

Closed
BorisBoutillier wants to merge 1 commit intobevyengine:mainfrom
BorisBoutillier:remove_duplicate_test_asserts
Closed

[Merged by Bors] - Remove duplicate asserts in test#5648
BorisBoutillier wants to merge 1 commit intobevyengine:mainfrom
BorisBoutillier:remove_duplicate_test_asserts

Conversation

@BorisBoutillier
Copy link
Contributor

Objective

While poking around the hierarchy code, I wondered why some asserts in tests were duplicated.
Some git blame later, I found out that commit ( 8eb0440 ) added already existing asserts while removing others.

Solution

Remove the duplicated asserts.

Copy link
Contributor

@TimJentzsch TimJentzsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me :)

Copy link
Contributor

@Weibye Weibye left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@Weibye Weibye added S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it C-Testing A change that impacts how we test Bevy or how users test their apps A-Hierarchy C-Code-Quality A section of code that is hard to understand or change labels Aug 10, 2022
@mockersf
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Aug 15, 2022
# Objective

While poking around the hierarchy code, I wondered why some asserts in tests were duplicated.
Some git blame later, I found out that commit ( 8eb0440 ) added already existing asserts while removing others.

## Solution

Remove the duplicated asserts.
@bors
Copy link
Contributor

bors bot commented Aug 15, 2022

Build failed:

@mockersf
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Aug 15, 2022
# Objective

While poking around the hierarchy code, I wondered why some asserts in tests were duplicated.
Some git blame later, I found out that commit ( 8eb0440 ) added already existing asserts while removing others.

## Solution

Remove the duplicated asserts.
@bors
Copy link
Contributor

bors bot commented Aug 15, 2022

@bors bors bot changed the title Remove duplicate asserts in test [Merged by Bors] - Remove duplicate asserts in test Aug 15, 2022
@bors bors bot closed this Aug 15, 2022
@BorisBoutillier BorisBoutillier deleted the remove_duplicate_test_asserts branch August 16, 2022 06:25
maccesch pushed a commit to Synphonyte/bevy that referenced this pull request Sep 28, 2022
# Objective

While poking around the hierarchy code, I wondered why some asserts in tests were duplicated.
Some git blame later, I found out that commit ( bevyengine@8eb0440 ) added already existing asserts while removing others.

## Solution

Remove the duplicated asserts.
james7132 pushed a commit to james7132/bevy that referenced this pull request Oct 28, 2022
# Objective

While poking around the hierarchy code, I wondered why some asserts in tests were duplicated.
Some git blame later, I found out that commit ( bevyengine@8eb0440 ) added already existing asserts while removing others.

## Solution

Remove the duplicated asserts.
ItsDoot pushed a commit to ItsDoot/bevy that referenced this pull request Feb 1, 2023
# Objective

While poking around the hierarchy code, I wondered why some asserts in tests were duplicated.
Some git blame later, I found out that commit ( bevyengine@8eb0440 ) added already existing asserts while removing others.

## Solution

Remove the duplicated asserts.
@alice-i-cecile alice-i-cecile added A-ECS Entities, components, systems, and events and removed A-Hierarchy labels Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-ECS Entities, components, systems, and events C-Code-Quality A section of code that is hard to understand or change C-Testing A change that impacts how we test Bevy or how users test their apps S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants