The set_audit_config_direct.js test verifies whether the setAuditConfig command functions as expected. It is skipped if the AuditConfigClusterParameter is enabled, which it is by default in 7.1 and generally in our all feature flags variants. The setAuditConfig command is still meant to function when that flag is enabled though, so we're currently missing coverage.

I attempted to enable the test but kept running into an RuntimeAuditConfigurationNotEnabled error, regardless of the value specified for --auditRuntimeConfiguration. It's possible I was configuring it wrong, but it's also possible that the command doesn't work properly under these conditions.