Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enforce expectation names uniqueness in CheckResultOutline test #1549

Merged
merged 1 commit into from
Jun 20, 2023

Conversation

nelsonkopliku
Copy link
Member

@nelsonkopliku nelsonkopliku commented Jun 20, 2023

Description

This should remove flakiness for the specific test changed.

@nelsonkopliku nelsonkopliku self-assigned this Jun 20, 2023
@nelsonkopliku nelsonkopliku added chore javascript Pull requests that update Javascript code test labels Jun 20, 2023
Copy link
Member

@EMaksy EMaksy left a comment

Choose a reason for hiding this comment

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

Yeah it's a lot more consistent this way :D
LGTM :D

Copy link
Contributor

@dottorblaster dottorblaster left a comment

Choose a reason for hiding this comment

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

LGTM but since those are strings, could we just use uuids?

@nelsonkopliku nelsonkopliku force-pushed the enforce-unique-expectation-names-in-tests branch from b08c9d2 to 9bdb891 Compare June 20, 2023 09:18
const expectationName3 = faker.color.human();
const expectSameExpectationName1 = faker.lorem.word();
const expectSameExpectationName2 = faker.lorem.word();
const expectationName1 = faker.datatype.uuid();
Copy link
Member Author

Choose a reason for hiding this comment

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

@dottorblaster I applied the suggested change about uuids.

I am afraid, though, that the should expectation names be uuids? doubt might rise, which is not the case.

As long as it clear that we just want strings that are unique in a restricted context and not necessarily uuids, we should be good.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah I agree, for me it's clear, I don't know if you want to leave a comment or something 😅

@nelsonkopliku nelsonkopliku force-pushed the enforce-unique-expectation-names-in-tests branch from 9bdb891 to 0e14eae Compare June 20, 2023 09:35
@nelsonkopliku nelsonkopliku force-pushed the enforce-unique-expectation-names-in-tests branch from 0e14eae to 6e8074a Compare June 20, 2023 09:38
@nelsonkopliku nelsonkopliku merged commit 343ed1b into main Jun 20, 2023
@nelsonkopliku nelsonkopliku deleted the enforce-unique-expectation-names-in-tests branch June 20, 2023 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore javascript Pull requests that update Javascript code test
Development

Successfully merging this pull request may close these issues.

3 participants