From 89f4449612b1ec80c69283e95c18032448407669 Mon Sep 17 00:00:00 2001
From: Dan Jones <dan.jones@noc.ac.uk>
Date: Mon, 23 Jan 2023 15:42:04 +0000
Subject: [PATCH] fix: clearer grammar for token scenarios
---
features/adapter_token-valid.feature | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/features/adapter_token-valid.feature b/features/adapter_token-valid.feature
index 53fe89d..e0e105b 100644
--- a/features/adapter_token-valid.feature
+++ b/features/adapter_token-valid.feature
@@ -1,19 +1,19 @@
Feature: Is the token valid?
The adapter tokenValid method works as expected
- Scenario: If adapter has not authed token is invalid
+ Scenario: If adapter has not authed then the tokenValid returns false
Given valid config
When the adapter instance is created
Then tokenValid returns false
- Scenario: If credentials.expiry is in the future token is valid
+ Scenario: If credentials.expiry is in the future then the token is valid
Given valid config
When the adapter instance is created
When the auth method is called
When the token expiry is in the future
Then tokenValid returns true
- Scenario: If credentials.expiry is in the past token is invalid
+ Scenario: If credentials.expiry is in the past then the token is invalid
Given valid config
When the adapter instance is created
When the auth method is called
--
GitLab