Rather than just numbering the tests try to provide semi descriptive names
for what the tests are trying to cover. This also has the advantage of
meaning we can add more tests without having to keep the list of tests
ordered by existing number which should make it easier to understand what
we're testing and why.
Signed-off-by: Mark Brown <broonie@xxxxxxxxxx>
---
tools/testing/selftests/alsa/pcm-test.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/alsa/pcm-test.c b/tools/testing/selftests/alsa/pcm-test.c
index bc0cb3c481f2..614ccc52cece 100644
--- a/tools/testing/selftests/alsa/pcm-test.c
+++ b/tools/testing/selftests/alsa/pcm-test.c
@@ -516,9 +516,9 @@ static void test_pcm_time1(struct pcm_data *data,
}
static const struct time_test_def time_tests[] = {
- /* name format rate chan period buffer */
- { "test.time1", "S16_LE", 48000, 2, 512, 4096 },
- { "test.time2", "S16_LE", 48000, 2, 24000, 192000 },
+ /* name format rate chan period buffer */
+ { "S16.48k.2.small", "S16_LE", 48000, 2, 512, 4096 },
+ { "S16.48k.2.big", "S16_LE", 48000, 2, 24000, 192000 },
};
int main(void)
--
2.30.2
