-
Updated
Apr 1, 2022 - Java
mocking-framework
Here are 94 public repositories matching this topic...
They are all currently written in groovy; I'd like to migrate them to the build.gradle.kts format to make the whole project Kotlin-based.
I think this can be done in steps, migrating one build.gradle file at a time - not sure about it though.
Hey Guys,
I see an IllegalStateException when running one particular test.
What steps will reproduce the problem?
The following code fails each time it is run
Testcase:
package backend.model.posting
import backend.controller.exceptions.ConflictException
import backend.model.location.Location
import backend.model.user.UserAccount
import org.junit.Before
import org.
-
Updated
Nov 29, 2020 - Kotlin
-
Updated
Apr 2, 2022 - C++
-
Updated
Mar 14, 2022 - Objective-C
-
Updated
Feb 12, 2022 - TypeScript
-
Updated
Apr 1, 2022 - Swift
-
Updated
Apr 1, 2022 - TypeScript
-
Updated
Mar 15, 2022 - JavaScript
-
Updated
Mar 31, 2022 - Java
-
Updated
Apr 2, 2022 - Scala
-
Updated
Mar 25, 2022 - C#
-
Updated
Dec 9, 2020 - Go
-
Updated
Mar 23, 2022 - Pascal
-
Updated
Mar 23, 2022 - C
-
Updated
Mar 8, 2022 - Swift
-
Updated
Jun 21, 2019 - Swift
-
Updated
Sep 22, 2019 - Rust
-
Updated
Nov 26, 2020 - Python
-
Updated
Mar 8, 2022 - C#
-
Updated
Aug 31, 2021 - Apex
-
Updated
Jul 27, 2019 - Swift
-
Updated
May 23, 2020 - C#
-
Updated
Mar 10, 2022 - C
This Add method has trailing comma in parameters part.
type Calculator interface {
Add(a int,
b int,
) int
}
It causes error like this.
10:30: expected statement, found ')' (and 1 more errors)
Usage:
1. Copy the interface you want to mock
2. Run 'mokku'
3. Paste the mocked implementation that has been written to your clipboard
-
Updated
May 31, 2017 - Java
-
Updated
Mar 16, 2022 - C
-
Updated
Apr 1, 2022 - TypeScript
Improve this page
Add a description, image, and links to the mocking-framework topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the mocking-framework topic, visit your repo's landing page and select "manage topics."
It may help in some cases of debugging to see what is the registered worker's scope. I don't think there's a way to see the worker's scope in the DevTools, it only lists "clients".
We may also consider printing additional information: