deon/gnuk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

test update

Browse Source
This commit is contained in:
NIIBE Yutaka
2012-07-03 19:32:15 +09:00
parent 9ef97836c9
commit 324b648de8
4 changed files with 49 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
test/features/040_passphrase_change.feature
View File

@@ -49,3 +49,23 @@ Feature: setup pass phrase
Scenario: verify PW1 (2) again
Given cmd_verify with 2 and "new user pass phrase"
Then it should get success
Scenario: change PW1
Given cmd_change_reference_data with 1 and "new user pass phraseanother user pass phrase"
Then it should get success
Scenario: verify PW1 (1) again
Given cmd_verify with 1 and "another user pass phrase"
Then it should get success
Scenario: verify PW1 (2) again
Given cmd_verify with 2 and "another user pass phrase"
Then it should get success
Scenario: change PW3 (admin-full mode)
Given cmd_change_reference_data with 3 and "another admin pass phraseadmin pass phrase"
Then it should get success
Scenario: verify PW3 (admin-full mode)
Given cmd_verify with 3 and "admin pass phrase"
Then it should get success

6
test/features/201_setup_passphrase.feature
View File

@@ -20,13 +20,13 @@ Feature: setup pass phrase
Then it should get success
Scenario: reset pass phrase by reset code (in admin-full mode)
Given cmd_reset_retry_counter with 0 and "example reset code 000new user pass phrase"
Given cmd_reset_retry_counter with 0 and "example reset code 000another user pass phrase"
Then it should get success
Scenario: verify PW1 (1) again
Given cmd_verify with 1 and "new user pass phrase"
Given cmd_verify with 1 and "another user pass phrase"
Then it should get success
Scenario: verify PW1 (2) again
Given cmd_verify with 2 and "new user pass phrase"
Given cmd_verify with 2 and "another user pass phrase"
Then it should get success

8
test/features/202_keygen.feature
View File

@@ -21,10 +21,10 @@ Feature: key generation
And put the second data to d0
Then it should get success
Scenario: verify PW1 (1) after genkey
Given cmd_verify with 1 and "new user pass phrase"
Scenario: verify PW1 (1) after keygen
Given cmd_verify with 1 and "another user pass phrase"
Then it should get success
Scenario: verify PW1 (2) after genkey
Given cmd_verify with 2 and "new user pass phrase"
Scenario: verify PW1 (2) after keygen
Given cmd_verify with 2 and "another user pass phrase"
Then it should get success

24
test/features/203_passphrase_change.feature
View File

@@ -15,11 +15,11 @@ Feature: setup pass phrase
Then it should get success
Scenario: setup reset code again (in admin-full mode)
Given cmd_put_data with d3 and "example reset code 000"
Given cmd_put_data with d3 and "example reset code 111"
Then it should get success
Scenario: reset pass phrase by reset code (in admin-full mode)
Given cmd_reset_retry_counter with 0 and "example reset code 000new user pass phrase"
Given cmd_reset_retry_counter with 0 and "example reset code 111new user pass phrase"
Then it should get success
Scenario: verify PW1 (1) again
@@ -49,3 +49,23 @@ Feature: setup pass phrase
Scenario: verify PW1 (2) again
Given cmd_verify with 2 and "new user pass phrase"
Then it should get success
Scenario: change PW1
Given cmd_change_reference_data with 1 and "new user pass phraseanother user pass phrase"
Then it should get success
Scenario: verify PW1 (1) again
Given cmd_verify with 1 and "another user pass phrase"
Then it should get success
Scenario: verify PW1 (2) again
Given cmd_verify with 2 and "another user pass phrase"
Then it should get success
Scenario: change PW3 (admin-full mode)
Given cmd_change_reference_data with 3 and "another admin pass phraseadmin pass phrase"
Then it should get success
Scenario: verify PW3 (admin-full mode)
Given cmd_verify with 3 and "admin pass phrase"
Then it should get success