Suggestions for Episode 2

[artem-zinnatullin]

Suggestions for Episode 2

[Gi-lo]

You could talk about:

• TDD and BDD
• Type of tests (Unit, UI, Integration, Regression)
• Mocking and Stubbing (e.g. for network requests)
• Available frameworks (Robolectric, Spock, AssertJ, RxPresso)
• Test Coverage (And why 100% should not be your goal)
• Ways to make your code testable (Separate logic from view, Dependency Injection, inversion of control)
• What to test and what not to test.

Also personally I would love to know more about https://jetbrains.github.io/spek/docs.html and testing with Kotlin at all.

[artem-zinnatullin]

@Gi-lo most of the things were already in the list, but thanks a lot, added some from your list!

[artem-zinnatullin]

@Gi-lo just wanted to say that

TDD vs BDD

Is not correct comparison :)

[Gi-lo]

Yeah you can actually do both ;) It's more like: TDD and BDD

[b1uebyte]

— Should QAs write some kind of tests? Or that exclusively developer's concern?
— Why do we want simulator? Is there any perspectives on that field?
— How to organize workflow in team to do better testing?

[artem-zinnatullin]

@b1uebyte great questions, added to the list, thanks!

[aleksandr-deich]

What should we do to make 1000+ lines activity testable?

[artem-zinnatullin]

@DeychAI great question, added to the list!

[sockeqwe]

I would love to hear your and your guests opinion on if it makes sense to write unit tests and functional UI "integration" tests (i.e. with espresso and only mocking the backend responses) or should we only write functional UI tests since they will test the underlying layers as well. Does testing the underlying layers again with single unit test for each layer / class make sense (testing underlying layers twice, one time with functional UI test, one time with his own unit test)?

[artem-zinnatullin]

@sockeqwe got it, will definitely discuss that, thanks!