You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While keeping unit tests in the same package as code is useful (so that we can test package scope code), this is less important for integration tests. Moving integration tests to a separate package would provide some benefits, such as allowing us to catch issues related to member variable access.
I have seen other projects (hibernate?) putting integration tests in a different module and package with respect to the code they test, so this is a good suggestion IMO.
Activity
jgeewax commentedon Jan 26, 2016
The example brings up a fair point -- tough to argue with that. Is this at all standard is other libraries like ours ?
mziccard commentedon Jan 26, 2016
I have seen other projects (hibernate?) putting integration tests in a different module and package with respect to the code they test, so this is a good suggestion IMO.
deps: update dependency com.google.apis:google-api-services-cloudreso…
chore: release 1.0.0 (googleapis#585)
chore(main): release 0.14.7 (#580)
chore(deps): update dependency com.google.cloud:google-cloud-retail t…
chore(deps): update dependency com.google.cloud:google-cloud-security…
chore(main): release 2.0.0 (#739)
chore: release 0.122.4-SNAPSHOT (#580)
chore(deps): update dependency com.google.cloud:google-cloud-datastor…
deps: update dependency com.google.http-client:google-http-client-bom…
chore(master): release 0.24.1 (#582)
deps: update dependency com.google.http-client:google-http-client-bom…
chore(master): release 0.24.1 (#582)
ci: removing linkage-monitor from the required checks (googleapis#580)
chore(deps): update dependency com.google.cloud:google-cloud-nio to v…
chore(deps): update dependency com.google.cloud:google-cloud-nio to v…
chore: regenerate README (#580)
chore: regenerate README (#580)
chore: move gfe metrics readme (googleapis#580)