Following up the results and recommendations of SPM-3904, in order to avoid a wrong usage of the transaction API in our tests, which could impact negatively developer productivity by causing test only fixes bf's, we should add a new evergreen task in the static analysis variant that ensures newly added js tests are properly using the txn API. We could follow a similar approach to SERVER-97430, checking if the added file is a jstests, and if it's running transactions, ensure the txn api is used, or, by investigating about special linting rules in javascript.