# Experiment: Adjusting SETA to run individual files instead of individual jobs

DevFeed: [Experiment: Adjusting SETA to run individual files instead of individual jobs](<https://devfeed.tech/articles/experiment-adjusting-seta-to-run-individual-files-instead-of-individual-jobs-20259.md>)

Original publisher: [Read original article](<https://elvis314.wordpress.com/2018/08/27/experiment-adjusting-seta-to-run-individual-files-instead-of-individual-jobs/>)

Author: elvis314

Published: 2018-08-27T18:17:18Z

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>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [code-coverage](<https://devfeed.tech/tags/code-coverage.md>), [experiment](<https://devfeed.tech/tags/experiment.md>), [test](<https://devfeed.tech/tags/test.md>), [tests](<https://devfeed.tech/tags/tests.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

## AI overview

The article reports an experiment to adjust SETA so it selects individual failing test files rather than entire test jobs. The experiment identified 171 tests and ran them in six jobs, while noting limitations involving failure types, configuration load balancing, and the effort required to produce unique test failures.

## Source excerpt

3.5 years ago we implemented and integrated SETA. This has a net effect today of reducing our load between 60-70%. SETA works on the premise of identifying specific test jobs that find real regressions and marking them as high priority. ... Continue reading ->