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

Public test fixtures for assertions on Kotlin DSL IDE editor script dependency resolution #9263

Closed
dsvoronin opened this issue Nov 9, 2018 · 2 comments
Labels

Comments

@dsvoronin
Copy link

We need API to emulate script resolving in tests

Expected Behavior

kotlinBuildScriptModelFor() or something similair is public and a part of some testing library

Current Behavior

I had to copypaste ~200 loc of KotlinBuildScriptModelRequest.kt
to be able to test this behavior

Context

IDE script resolving could fail while cli configuration successful.
How this could happen?
resolving mechanism trigger build configuration to resolve dependencies, and do so in some "sandbox" environment, it could lead to errors during script resolution. For example i had .sh script fail that called something git related, because during IDE resolution .git was not available

To prevent merging such code and as result 'red' scripts on developer machines we want to mimic IDE resolving mechanism and run it during CI checks.

@eskatos eskatos changed the title Ability to test script resolving Ability to test IDE editor script dependency resolution Nov 9, 2018
@eskatos eskatos changed the title Ability to test IDE editor script dependency resolution Public test fixtures for assertions on IDE editor script dependency resolution Apr 24, 2019
@eskatos eskatos changed the title Public test fixtures for assertions on IDE editor script dependency resolution Public test fixtures for assertions on Kotlin DSL IDE editor script dependency resolution Apr 24, 2019
@eskatos eskatos transferred this issue from gradle/kotlin-dsl-samples Apr 25, 2019
@stale
Copy link

stale bot commented Sep 6, 2020

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@stale stale bot added the stale label Sep 6, 2020
@stale
Copy link

stale bot commented Sep 27, 2020

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.

@stale stale bot closed this as completed Sep 27, 2020
@wolfs wolfs closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants