Integration testing #1

New Issue

oysteikt · 2024-12-02T06:45:39+01:00

oysteikt commented

2024-12-02 06:45:39 +01:00

It would be nice if we could integration test the implementation against the mpd daemon. I'm imagining the best way to do this would be to create a test harness that runs a separate instance of mpd for every single test, with a predetermined state and configuration. Then the test for a single command would run any necessary setup commands to get mpd into a state where it makes sense to run the command in question.

We need to make sure that only n amount of tests are ever run simultaneously in order to to kill the host with literally 100 instances of mpd.

Be sure to add a few songs and artists and such with labels that might be confusing for the parsers (e.g OK, list_ok, \n, \t, <space>, weird UTF-8 chars, ...)

It would be nice if we could integration test the implementation against the mpd daemon. I'm imagining the best way to do this would be to create a test harness that runs a separate instance of mpd for every single test, with a predetermined state and configuration. Then the test for a single command would run any necessary setup commands to get mpd into a state where it makes sense to run the command in question. We need to make sure that only n amount of tests are ever run simultaneously in order to to kill the host with literally 100 instances of mpd. Be sure to add a few songs and artists and such with labels that might be confusing for the parsers (e.g `OK`, `list_ok`, `\n`, `\t`, `<space>`, weird UTF-8 chars, ...)

oysteikt added this to the (deleted) project 2024-12-18 23:29:08 +01:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Grzegorz/empidee#1