https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
t

tim

07/13/2020, 7:51 PM
Hello, i'm trying to write e2e tests across several micro services. I'd like include various micro services in an e2e project but I'm encountering build issues when including them via settings.gralde.kts. For example, one of the included projects, (which is part of a multi project micro service), is causing build errors (i.e., "Unresolved reference" for an included plugin). Has anyone had success with this type of setup or is there a better approach? I'm going to try symlinking these services into my e2e-testing project next, but that feels a bit hacked together.
d

Dariusz Kuc

07/13/2020, 7:55 PM
if your project builds custom plugin AFAIK you cannot apply it to other projects within the same build
you will need to use composite build
t

tim

07/13/2020, 7:56 PM
okay i haven't used composite builds but the gradle description seems about right
i had considered git submodules as an alternative as well
d

Dariusz Kuc

07/13/2020, 7:57 PM
dont think the git submodules will help you
i.e. gradle first will configure the project and then run build
so for configuration you would need the plugin to be already build
t

tim

07/13/2020, 7:58 PM
i already use git sub modules in a similar fashion where every micro service includes a core + testing submodule
d

Dariusz Kuc

07/13/2020, 7:59 PM
libs should be fine as they are just dependencies
plugins -> cant do
t

tim

07/13/2020, 7:59 PM
what do you mean by plugin?
d

Dariusz Kuc

07/13/2020, 8:01 PM
does your build create custom gradle plugin?
t

tim

07/13/2020, 8:01 PM
no
d

Dariusz Kuc

07/13/2020, 8:02 PM
then you shouldnt have to do the composite builds
*you could if it makes for simpler config
t

tim

07/13/2020, 8:02 PM
at least i don't think so 😂 I'm just using the application plugin invoke my entry point/main function
i must admit I don't have a good handle on gradle
i'll dig into composite builds because ... learnings 🙂 maybe it'll solve some of our project setup challenges!
I've just done a small experiment with composites to include the projects i'm currently include as git submoduls ... composites seem promising
seems straightforward when including a simple project, but when including a multi-project, I cant import from it into my composite project. This is what i'm trying to do:
// composite's settings.gradle.kts
include(
  "e2et"
)
project(":e2et").projectDir = File("projects/e2et")
includeBuild("../core")
includeBuild("../multi-project")
and then
// projects/ete2/build.gradle.kts

dependencies {
    ...
    implementation(":core")
    implementation(":multi-project:a")
     ...
}
And finally:
// e2et/src/main/kotlin/App.kt
package e2et

import core.Id
import a.SomethingFromA

main() {
  val somethingFromCore = Id() // works
  val f = SomethingFromA() // doesn't work
}
Ahh got it to work! Just needed to replace
mplementation(":multi-project:a")
with
mplementation("multi-project:a")
this looks brilliant i think i might remove all git modules in preference for composites!
t

tddmonkey

07/14/2020, 7:23 AM
Rather than doing this - have you considered just deploying your services somewhere and testing against that?
t

tim

07/14/2020, 7:32 AM
So thats exactly what I am doing ... however in writing the tests I need access to the state data classes, repository helpers, etc without having to duplicate them again inside my tests
So plan for my e2e test composite project is to have a target environment to test against which could be local, or a remote deployment and then run the tests against it
t

tddmonkey

07/14/2020, 7:59 AM
Feel free to tell me to mind my own business - but if you’re doing e2e tests against multiple services, how come you need access to the source code at all? Isn’t it all done via APIs?
t

tim

07/14/2020, 8:07 AM
It is for the most part yes! There are several reason why I want access to the source code (happy to be told a better way though 🙏) • We have graphql end points with type safe clients and I don't want to rewrite these • The domain models that are built by the endpoints are complex enough that in each micro service I've built test helpers to create these objects to then be sent to the endpoint ... i don't want to rewrite these and if a change is made in the service then I want type checking to help identify new/missing types to update • In some instances an API is not finished and so I need to be able to change a value inside our db (i.e., stuff like changing a status from DRAFT -> APPROVED) in that instance I'd like to use the repository helpers we've built rather than directly accessing the database to tweak a value (again type safety will help keep everything up to date as our system evolves) I"m sure there are more reasons, but being lazy and not wanting to duplicate code is the primary one :)