Skip to content

Commit a4a4a39

Browse files
committed
Update add_factor_integration.rs
1 parent 8c72c50 commit a4a4a39

1 file changed

Lines changed: 1 addition & 7 deletions

File tree

tests/add_factor_integration.rs

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -103,9 +103,6 @@ async fn parse_response_body(response: Response) -> Value {
103103
serde_json::from_slice(&body).unwrap()
104104
}
105105

106-
/// Drives a full `/add-factor` request that adds a new Google OIDC factor for `subject`, returning
107-
/// the raw response. Generates a fresh keypair, OIDC token, challenges, and passkey assertion on
108-
/// every call, so it can be invoked repeatedly for the same subject.
109106
async fn add_google_oidc_factor(
110107
oidc_server: &MockOidcServer,
111108
environment: Environment,
@@ -154,12 +151,9 @@ async fn add_google_oidc_factor(
154151
.await
155152
}
156153

157-
// A factor rejected because the backup is already at `MAX_MAIN_FACTORS_PER_BACKUP` must have its
158-
// `FactorLookup` entry rolled back. Otherwise the rejected credential stays mapped to the backup and
159-
// later attempts to use or re-register it fail until manual cleanup.
160154
#[tokio::test]
161155
#[serial]
162-
async fn test_add_factor_at_max_limit_rolls_back_lookup() {
156+
async fn test_add_factor_at_max_limit_rolls_back_factor_lookup() {
163157
let (oidc_server, environment, backup_id, mut passkey_client) = setup_test_environment().await;
164158

165159
// The backup starts with one passkey factor; seed distinct OIDC factors up to the limit.

0 commit comments

Comments
 (0)