# System tests of metricbeat modules **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [March 25, 2019, 10:24pm UTC](https://discuss.elastic.co/t/system-tests-of-metricbeat-modules/173834 "2019-03-25T22:24:08Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![berfinsari](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/berfinsari/32/33839_2.png) [@berfinsari](https://discuss.elastic.co/u/berfinsari)\ **Post date:** [March 25, 2019, 10:24pm UTC](https://discuss.elastic.co/t/system-tests-of-metricbeat-modules/173834/1 "2019-03-25T22:24:08Z")
I wonder something about system tests of metricbeat modules. Some system tests are in the metricbeat/module/{module} directory instead of metricbeat/test/system directory. Because of this, `MODULE={module} make test-module` command returns an error that the module does not have a system test. What can I do to prevent this error? ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [March 29, 2019, 3:41pm UTC](https://discuss.elastic.co/t/system-tests-of-metricbeat-modules/173834/2 "2019-03-29T15:41:40Z")
I forgot we had this Makefile command, I always run these manually. The initial plan was to migrate all module system tests to the module itself to have everything together. As a workaround for now, I would recommend to just build the command manually. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 26, 2019, 3:41pm UTC](https://discuss.elastic.co/t/system-tests-of-metricbeat-modules/173834/3 "2019-04-26T15:41:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.