Skip to content
This repository has been archived by the owner on Nov 18, 2019. It is now read-only.

Employ Test-Driven Design to create robust Services. #12

Open
wrichter opened this issue Apr 12, 2019 · 5 comments
Open

Employ Test-Driven Design to create robust Services. #12

wrichter opened this issue Apr 12, 2019 · 5 comments
Labels
kind/architecture

Comments

@wrichter
Copy link
Contributor

wrichter commented Apr 12, 2019 •
edited
Loading

I see Tdd relevant on two different but related areas:

  • testing interfaces independent of their implementations, e.g. when implementations can be exchanged (eg. SpotifyBackend vs. AmazonMusicBackend or SimplePlaybackController vs. FadingAndBeatsAligningPlaybackController)
  • testing component behavior spanning multiple interfaces (e.g. PlayList Service emitting an event after the playlist has been changed via Front API)
@wrichter
Copy link
Contributor Author

Depends on #11

@wrichter
Copy link
Contributor Author

wrichter commented Apr 24, 2019 •
edited
Loading

I've added a first set of ideas to describe a possible approach to TDD here: https://github.com/sa-mw-dach/OpenDJ/blob/master/meta/developmenapproach.md

@wrichter wrichter mentioned this issue Apr 24, 2019
Open
@DanielFroehlich
Copy link
Collaborator

I like the approach in general - we have to find out what is workable for us and what not.

@DanielFroehlich
Copy link
Collaborator

currently, I cant see any ressources for this. Suggest to defere this after MVP implementation. Or would anybody help on this?

@DanielFroehlich DanielFroehlich mentioned this issue Jun 15, 2019
Open
@DanielFroehlich
Copy link
Collaborator

dropped for current sprint

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/architecture
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wrichter @DanielFroehlich