On Fri, May 21, 2021 at 11:29 AM Peter Maydell <peter.mayd...@linaro.org> wrote: > > On Fri, 21 May 2021 at 15:19, Philippe Mathieu-Daudé <f4...@amsat.org> wrote: > > If you think these tests belong to tests/tcg/, I am OK to put > > them they, but I don't think adding the Avocado buildsys > > machinery to the already-complex tests/tcg/ Makefiles is going > > to help us... > > This does raise the question of what we're actually trying > to distinguish. It seems to me somewhat that what tests/acceptance/ > actually contains that makes it interestingly different from other > tests/ stuff is that it's specifically "tests using the Avocado > framework". On that theory we might name it tests/avocado/. > > Or we could just leave it as it is -- is the current naming > actually confusing anybody? :-)
Conceptually speaking, it isn't very clear because acceptance tests are meant to test features requested by the customer during the requisite phase for a specific software release. The QEMU project does not have a formal requisite phase where features added to one software version are discussed with the customers. In this case, the QEMU acceptance tests are not accepting a use case or requested feature of a release. Eventually, those tests may not be a blocker to a release if some of them fail. Thus, calling them acceptance, may confuse people working with tests. > > thanks > -- PMM >
