profile
viewpoint
Steve Moyer smoyer64 The Pennsylvania State University Boalsburg, PA

selesy/uprest 13

upREST - Verify your REST services with this JUnit5 extension

smoyer64/cdi-unit 1

Unit testing for CDI applications

selesy/additional-properties 0

Provides a generator to allow struct marshaling and unmarshaling of arbitrary fields

selesy/json-star 0

Wraps Go's standard library JSON processing to handle additional properties

selesy/sundhet 0

Service that provides application healthcheck for Kubernetes

smoyer64/ansible 0

Model-driven configuration management, multi-node deployment/orchestration, and remote task execution system. Uses SSH by default, so there is no special software has to be installed on the nodes you manage. Ansible can be extended in any language. Note: The default branch is the development branch which many people run directly from checkout, if you need a stable version, see the release-XX branches, tags, or ansible.cc/releases.

smoyer64/challenges 0

Repo for our weekly challenges on pybit.es

startedbentoml/BentoML

started time in 10 hours

push eventjunit-team/junit5

Marc Philipp

commit sha d1234f1c23eef133c68283faa58ccac048cdfcd5

Use javaLanguageVersion if its less than 15

view details

push time in 15 hours

push eventjunit-team/junit5

Marc Philipp

commit sha f35ec81e2dfaaa7d4ba3373e0966d8070c17693e

Enable build scans and build cache for CodeQL builds

view details

push time in 16 hours

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

Fun thing (not sure if "fun" is that right ;)) is that if you drop the "if private fail" check it works on private fields :(.

rmannibucau

comment created time in 16 hours

push eventsmallrye/smallrye-config

Roberto Cortez

commit sha f730ed26dac371f374023e0338f6a3169ff8c632

Use random port in test.

view details

push time in 16 hours

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

At this point I don't think it's worth the added complexity.

rmannibucau

comment created time in 16 hours

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

@marcphilipp I can understand that as well. How about an engine parameter "allowedVisibility"? I know it is a toggle but not a crazy one IMHO.

rmannibucau

comment created time in 17 hours

push eventjunit-team/junit5

Marc Philipp

commit sha 047f739852d4d29b21f329c9ef9b6325df88a626

Pin Groovy compilation to use JDK 15 for now

view details

push time in 17 hours

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

I can understand your use case but it would be inconsistent to allow private on fields but not on methods and I really don't want to allow it for methods. 😕

rmannibucau

comment created time in 17 hours

push eventjunit-team/junit5

Marc Philipp

commit sha d54bb96ebd55a84b756ebb1792d702d33a038b20

Upgrade Groovy for JDK 16 support

view details

push time in 17 hours

push eventjunit-team/junit5

Marc Philipp

commit sha fdac06b72901f83da28691019cfc305e1163d7a0

Upgrade test-retry plugin to 1.2.0

view details

Marc Philipp

commit sha 072b480061d955cec889d4c62f7de8e2b87059df

Upgradle to 6.8-rc-1

view details

push time in 18 hours

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

@marcphilipp yep, funnily I was not "hit" by that on methods (guess rules I used are not very strict for methods).

rmannibucau

comment created time in 18 hours

issue commentsmallrye/smallrye-config

Support for Map<String, T> and List<T>

Ah, probably because we only assign the outer most key if the inner keys are part of a list. Let me have a look.

vsevel

comment created time in 19 hours

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

IIUC you're mostly concerned about fields not allowed to be private with @RegisterExtension?

rmannibucau

comment created time in 19 hours

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

@marcphilipp cause it is common to enable private fields and forbids protected or package ones due to the leak it does (regarding encapsulation). In other words it means your test style can't be your main code style (mixed with nested test classes it starts to becomes hard to validate but even when physically split it not not good to code differently depending folders of the same project IMHO). More techincally, on an IDE point of view you get completion from friend classes which is also a noise you don't desire when writing tests IMHO. Hope it is clearer written this way.

rmannibucau

comment created time in 20 hours

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

What violates style validations?

rmannibucau

comment created time in 20 hours

issue closedjunit-team/junit5

Passing TestExecutionListener to engine launched by EngineTestKit

In junit-pioneer/junit-pioneer#375, we failed to write an integration test for an extension because it includes a TestExectionListener and the test run we launch with EngineTestKit didn't pick it up (at least it didn't call methods like reportingEntryPublished and executionFinished for the tests executed by that engine). Is that behavior intentional?

If so and it can't be changed (it would be somewhat weird to have an execution listener that listens to both the actual Jupiter run, but then also to the engine launched during one of those tests), it would be nice if we'd be able to register a listener explicitly. The EngineExecutionListener comes close, but I didn't find a way to register our own implementation.

closed time in 21 hours

nipafx

issue commentjunit-team/junit5

Passing TestExecutionListener to engine launched by EngineTestKit

Team decision: The EngineTestKit is meant for testing engines. We had originally envisioned potentially adding a LauncherTestKit or sth. similar later. If you need to integration test with a TestExecutionListener, please use the Launcher API directly for the time being.

nipafx

comment created time in 21 hours

issue closedjunit-team/junit5

[IJ IDE] JUnit Jupiter Assumptions do not work in @BeforeAll methods

I am still seen this issue on intelliJ

org.junit.jupiter junit-jupiter-api 5.7.0 test IntelliJ IDEA 2020.2.4 (Community Edition) Build #IC-202.8194.7, built on November 24, 2020 Runtime version: 11.0.9+11-b944.49 x86_64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 10.16 GC: ParNew, ConcurrentMarkSweep Memory: 725M Cores: 8

image

closed time in 21 hours

Diego11914

issue commentjunit-team/junit5

[IJ IDE] JUnit Jupiter Assumptions do not work in @BeforeAll methods

@BeforeAll methods have to be static unless you change the default test instance lifecycle to PER_CLASS.

Diego11914

comment created time in 21 hours

issue commentjunit-team/junit5

Add Assumptions.assumeDoesNotThrow

Team decision: Your request sounds reasonable, but we're unsure how generally useful it is given it hasn't been requested before. Thus, changing the status to "waiting for interest".

ST-DDT

comment created time in 21 hours

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

Side note: it violates several style validations and common practises in terms of visibility (why Test2 can check Test1 extensions?), in particular when integrating with 3rd parties (which almost all allows private injections) so overal it makes the test class inconsistent. Any hope it gets revised with wider scope than just junit scope?

rmannibucau

comment created time in 21 hours

issue closedjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

Hi,

In java there is no real reason to support package scope member but not private ones so let's drop that constraint in next release please.

Romain

closed time in 21 hours

rmannibucau

issue commentjunit-team/junit5

Allow fields, methods, and constructors in Jupiter to be private

Team decision: We support package-private methods because they're shorter to write and are in accordance with the convention of placing test classes in the same package as production code.

rmannibucau

comment created time in 21 hours

issue commentjunit-pioneer/junit-pioneer

Explore use of InvocationInterceptor to disable (parameterized) tests

After wasting about an hour, I learned that while we could use Parameter#getName, it only works if the information was included during compilation (which can be checked with Parameter#isNamePresent).

I've created an alternate approach that's index based. That's always available, at least.

nipafx

comment created time in a day

startedaalmiray/java-champions

started time in a day

pull request commentavelino/awesome-go

Update go-git with its new GitHub org

Thank you for contributing with awesome-go, we will revise your contribution as soon as possible.

Automation body links content check:

  • godoc.org or pkg.go.dev: True
  • goreportcard.com: False
  • coverage: False

your project is about to be approved, it's under revision, it may take a few days

nicerobot

comment created time in a day

PR opened avelino/awesome-go

Update go-git with its new GitHub org

src-d/go-git is archived. go-git/go-git is the new org/repo.

+1 -1

0 comment

1 changed file

pr created time in a day

issue openedjunit-team/junit5

[IJ IDE] JUnit Jupiter Assumptions do not work in @BeforeAll methods

I am still seen this issue on intelliJ

org.junit.jupiter junit-jupiter-api 5.7.0 test IntelliJ IDEA 2020.2.4 (Community Edition) Build #IC-202.8194.7, built on November 24, 2020 Runtime version: 11.0.9+11-b944.49 x86_64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 10.16 GC: ParNew, ConcurrentMarkSweep Memory: 725M Cores: 8

image

created time in a day

more