# running tests by bugzilla component instead of test suite

DevFeed: [running tests by bugzilla component instead of test suite](<https://devfeed.tech/articles/running-tests-by-bugzilla-component-instead-of-test-suite-20258.md>)

Original publisher: [Read original article](<https://elvis314.wordpress.com/2017/12/21/running-tests-by-bugzilla-component-instead-of-test-suite/>)

Author: elvis314

Published: 2017-12-21T17:07:44Z

Content type: article

Language: en

Sources: [Mozilla Automation](<https://devfeed.tech/sources/mozilla-automation.md>)

Topics: [test-coverage](<https://devfeed.tech/topics/test-coverage.md>), [Test coverage](<https://devfeed.tech/topics/coverage.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [testdev](<https://devfeed.tech/tags/testdev.md>), [tests](<https://devfeed.tech/tags/tests.md>), [tools](<https://devfeed.tech/tags/tools.md>), [treeherder](<https://devfeed.tech/tags/treeherder.md>)

## AI overview

The article explores running tests by Bugzilla component instead of test suite or random chunks. It describes potential benefits including component-level code coverage, more deterministic SETA results, component filtering in Treeherder, and easier handling of intermittent tests, while noting that the approach is not production-ready.

## Source excerpt

Over the years we have had great dreams of running our tests in many different ways. There was a dream of 'hyperchunking' where we would run everything in hundreds of chunks finishing in just a couple of minutes for all ... Continue reading ->