@mkporwit also tried with

2018.1

and it works.

@mkporwit you could try to add junit as dependency to your project. IntelliJ should then provide a menu where you can choose "Run all Specs" and "Run all Tests". Speaking of that, did you chose "Run all Tests" once? Maybe IntelliJ does no longer provide "Run all Specs" due to this.

Is it a good time to start using Spek 1.1? I mean, since 2.0 is not so far away, wouldn't it require long/painful migration that may not be worth it for the wait?

@raniejade Not sure what happened, but suddenly, I can do “Run specs in <package>“. Yay, my life is good again 🙂

One thing I miss in the IntelliJ plugin is the ability to jump on double-click. Any way to get that today or is that a 2.x feature? https://github.com/raniejade/spek-idea-plugin/issues/65

One thing I miss in the IntelliJ plugin is the ability to jump to source on double-click in the test results window. Any way to get that today or is that a 2.x feature? https://github.com/raniejade/spek-idea-plugin/issues/65

Hey, is there any way to abort sut (all following tests under some group, e.g. given) in spek? I’m using 1.1.5 and can’t find any sight of it 😞

Is there any published snapshots of 2.x releases to try?

hi, guys is any developers that facing issue using spek when upgrade AS 3.1.0 stable?

@raniejade if you had a time https://github.com/spekframework/spek-android-example/pull/2

Please review this PR

OK, now my real question! Problem is, I don't know if it's a problem with Spek, IntelliJ, my automation framework (Kirk) or my application server (spark-kotlin). I'm am running Selenium integration tests via kirk (http://automation-remarks.com/kirk/ ) on my spark-kotlin (http://sparkjava.com/ application. The tests launch the server, open a browser, enter some values and verify the results. All is good, all the tests run positively. But it never terminates. IntelliJ sits at running tests. When I run the tests via gradlew (thanks to @fred.deschenes) the tests complete, the browser closes and the server stops. This does not happen in IntelliJ.

I have the same experience when I run Spek tests with testcontainers. Terminated properly under gradlew, fails to under IntelliJ

@mkporwit @v79 you're probably hitting this issue: https://github.com/spekframework/spek/issues/345

Thanks @Czar - not a problem while I'm still experimenting.

Yeah, I wind up having to force terminate jobs under IntelliJ for now… maybe it’ll get fixed in 2.0?

hi, guys. i have an question. Supposed we have app that retrieve weather from api that had a function

fetchWeather

and the return have 2 closure

success

and

error

what is best structure to write it within spek? currently i did like this

app

interface WeatherRepository {
	fun fetchWeather() : Single<List<Weather>>	
}

class WeatherDataStore (private val service: WeatherService) : WeatherRepository {
	override fun fetchWeather() : Single<List<Weather>> {
		return service.fetchWeather()
					  .compose(singleIo())
	}
}


class WeatherPresenter (private val repository : WeatherRepository) {
	fun fetchWeather() {
		repository.fetchWeather().subscribe({ success -> 
			// todo
		}, { error ->
			// todo
		})
	}
}

test

class WeatherPresenterTest : Spek ({
	given("a weather presenter") {
		val repository 	= mock<WeatherRepository>()
		val view		= mock<WeatherView>()

		val presenter 	= WeatherPresenter(repository)

		beforeEachTest {
			presenter.attachView(view)
		}

		whenever("fetch weather") {
			then("return success") {
				repository.fetchWeather() willReturnSingle weatherData // this weatherData from fixture
				
				presenter.fetchWeather()

				verify(view).onLoadWeatherSuccess(weatherData)
				verifyNoMoreInteraction(view)
			}

			then("return error") {
				repository.fetchWeather() willReturnSingleError weatherDataError // this weatherData from fixture
				
				presenter.fetchWeather()

				verify(view).onLoadWeatherError(weatherDataError)
				verifyNoMoreInteraction(view)
			}
		}

		afterEachTest {
			presenter.detachView()
		}
	}
})

Hey all! We are planning to split Spek's DSLs in to different styles and completely isolating them from each other, to avoid users mixing and matching. This is discussed in this issue: https://github.com/spekframework/spek/issues/374. We would like to get your feedback/suggestions about this. Do note that the conversation focuses on isolation, how the DSL would look like for each style is a separate discussion.

@here Hi all, Is there any tutorial on how to test Api’s (Retrofit) with Spek? Any help would be much appreciated, thanks!

Is there any way to assign annotations in the form of Tags/Categories to Spek tests? What I'm looking at doing is, running only my Unit Tests in certain environments, and integration tests in another.

Anyone know if 2.0 branch is usable at all for multiplatform support?

As far as I know it is not ready yet but would be eager to try it out for JS 🙂

Not yet, unfortunately 🙁

ok, looking forward to it! If/when your looking for early users I may be interested

It’s been stalled on the current milestones for quite awhile. I keep meaning to pitch in, but work keeps getting in the way 😞

Is there any info about what’s changing? We have a pretty significant number of Spek tests here.

It’s a relatively significant change. I’m not aware of any concrete documentation for the changes, but you’re welcome to look at the GitHub repo and read the changes in the 2.x branch yourself: https://github.com/spekframework/spek

Looks like this is a good place to look at https://github.com/spekframework/spek/tree/2.x/samples/src/test/kotlin/org/spekframework/spek2/samples