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

Improve-test-coverage - AuditEventConverter, JdlMetadataService, YoRC… #247

Merged
merged 1 commit into from
Oct 15, 2020

Conversation

Strat1987
Copy link
Contributor

@Strat1987 Strat1987 commented Oct 11, 2020

Related to #213

@CLAassistant
Copy link

CLAassistant commented Oct 11, 2020

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@SudharakaP SudharakaP left a comment

Choose a reason for hiding this comment

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

@Strat1987 : Hi, thanks for submitting the PR. 😄

  1. Could you please sign the CLA.

  2. There seems to be a CI failure in the newly added file AuditEventConverterTest.java at line 59. I think there's a problem with the syntax.


-> at io.github.jhipster.online.config.audit.AuditEventConverterTest.convertToAuditEventNullEvent(AuditEventConverterTest.java:59)

You cannot use argument matchers outside of verification or stubbing.
Examples of correct usage of argument matchers:
    when(mock.get(anyInt())).thenReturn(null);
    doThrow(new RuntimeException()).when(mock).someVoidMethod(anyObject());
    verify(mock).someMethod(contains("foo"))

@Strat1987
Copy link
Contributor Author

  1. the version wouldn't load last time for the CLA, was successful this time around.
  2. Using IntelliJ test runner, this assertion does succeed, I do feel the implementation is strange since it adds null objects to the list. not empty check suffices as I'm only adding the null value, no need to explicitly assert it

@SudharakaP
Copy link
Member

SudharakaP commented Oct 13, 2020

@Strat1987 : The CLA doesn't seem to be signed yet. Did you already signed it? Maybe there's something wrong on our side? 🤔

cc: @pascalgrimaud

@pascalgrimaud
Copy link
Member

I think it's because the commits come from @roexber account, and you tried to sign the cla with @Strat1987 account

@SudharakaP
Copy link
Member

I think it's because the commits come from @roexber account, and you tried to sign the cla with @Strat1987 account

@pascalgrimaud : Thanks. Nice catch. 👍🏼

@roexber
Copy link
Contributor

roexber commented Oct 14, 2020

I've now accepted CLA using the github account I also used for the commits, apologies

@pascalgrimaud
Copy link
Member

No worry @roexber : don't be sorry for helping Open Source projects :-)

@SudharakaP
Copy link
Member

SudharakaP commented Oct 15, 2020

I've now accepted CLA using the github account I also used for the commits, apologies

@Strat1987 : No worries, thanks a bunch. Can you re-base and run prettier; npm run prettier:format so that we have the formatting consistent. 😄

EDIT: You don't have to run prettier as it's auto run on commit anyways. My mistake. 😢

@roexber
Copy link
Contributor

roexber commented Oct 15, 2020

@SudharakaP Done, It's a challenge for me performing this many history changing GIT commands which I'm really not accustomed with in my day to day.

@SudharakaP SudharakaP merged commit b5dfcaf into jhipster:master Oct 15, 2020
@SudharakaP
Copy link
Member

@roexber : Thanks much for your contribution. Looks awesome. 👍🏼

@roexber
Copy link
Contributor

roexber commented Oct 19, 2020

@SudharakaP thanks for the kind words. I'm happy to contribute since JHipster greatly helped in coming back to the spring eco system

@SudharakaP
Copy link
Member

SudharakaP commented Oct 19, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants