Project Number Date
ApolloFullRunnerReport 2021.AT1.25 30 lip 2021, 04:08

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Login feature 62 1 5 0 0 68 7 1 8 3m 2s 847ms Failed
Feature Login feature
Before Hooks.showScenarioName(Scenario) 000ms
Given Login as "hochland-admin" 2s 894ms
Then User is successfully logged 003ms
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-skd" 094ms
And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 002ms
Given Failed login as "swiss-krono-delivery-admin" 494ms
Then Verify that login error reason is "auth.invalidLoginOrPassword" 280ms
Given Try login as "swiss-krono-delivery-admin" 515ms
Then Verify that login error reason is "auth.accountLocked" 105ms
Given Click remind password button 069ms
And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 206ms
And Send remind password form with email "apolloautomattest@gmail.com" 153ms
When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 27s 129ms
And Extract password from mailgun mail 3s 785ms
And Reset password from link 654ms
Then Login as "swiss-krono-delivery-admin" 1s 271ms
And User is successfully logged 004ms
After Hooks.rollbackParameters() 002ms
After Hooks.unlockUsers() 088ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-neuca" 094ms
And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "3" 002ms
Given Failed login as "neuca-admin" 469ms
Then Verify that login error reason is "auth.invalidLoginOrPassword" 216ms
Given Failed login as "neuca-admin" 474ms
Then Verify that login error reason is "auth.invalidLoginOrPassword" 217ms
Then Login as "neuca-admin" 815ms
Given Failed login as "neuca-admin" 459ms
Then Verify that login error reason is "auth.invalidLoginOrPassword" 212ms
Then Login as "neuca-admin" 807ms
And User is successfully logged 008ms
After Hooks.rollbackParameters() 001ms
After Hooks.unlockUsers() 084ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-sempertrans" 095ms
And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 001ms
And Prepare parameter "BLOCKED_USER_DURATION_IN_MINUTES" with value: "1" 001ms
When Failed login as "sempertrans-admin" 438ms
And Verify that login error reason is "auth.invalidLoginOrPassword" 209ms
And Failed login as "sempertrans-admin" 481ms
And Verify that login error reason is "auth.accountLocked" 097ms
Then Wait "62" seconds 1m 2s
And Login as "sempertrans-admin" 1s 809ms
And User is successfully logged 003ms
After Hooks.rollbackParameters() 002ms
After Hooks.unlockUsers() 078ms
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-adama" 097ms
And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 001ms
And Prepare parameter "BLOCKED_USER_DURATION_IN_MINUTES" with value: "1" 001ms
When Failed login as "adama-admin" 451ms
And Verify that login error reason is "auth.invalidLoginOrPassword" 223ms
And Failed login as "adama-admin" 459ms
And Verify that login error reason is "auth.accountLocked" 045ms
Then Wait "62" seconds 1m 2s
And Login as "adama-admin" 1s 657ms
And User is successfully logged 003ms
After Hooks.rollbackParameters() 001ms
After Hooks.unlockUsers() 073ms
Scenario Outline Check if user is logged out when another person login on same account
Before Hooks.showScenarioName(Scenario) 000ms
Steps
Given Set token of apiUsername "super-admin-bausch" 092ms
And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "bausch-admin" 001ms
java.lang.AssertionError: Nie znaleziono szukanego zasobu w Apollo!
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getBigIntegerResult(ApolloSelectDbService.java:117)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getLongResult(ApolloSelectDbService.java:107)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.findIdBy(ApolloSelectDbService.java:19)
	at CucumberTests.Utils.AuthorityTest.removeBasicAuthoritiesToUser(AuthorityTest.java:62)
	at ✽.Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "bausch-admin"(file:Features/Atom/Logins/Login.feature:68)
And Login as "bausch-admin" 000ms
And Login as "bausch-admin" on another browser 000ms
And Close second browser 000ms
And Refresh page 000ms
Then Verify user is logged out 000ms
After Hooks.rollbackRemovedAuthorities() 000ms
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-farmacol" 092ms
And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "farmacol-admin" 055ms
And Login as "farmacol-admin" 1s 408ms
And Login as "farmacol-admin" on another browser 1s 903ms
And Close second browser 076ms
And Refresh page 2s 113ms
Then Verify user is logged out 035ms
After Hooks.rollbackRemovedAuthorities() 040ms
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-alrec" 097ms
And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "alrec-admin" 025ms
And Login as "alrec-admin" 1s 450ms
And Login as "alrec-admin" on another browser 1s 741ms
And Close second browser 073ms
And Refresh page 2s 122ms
Then Verify user is logged out 028ms
After Hooks.rollbackRemovedAuthorities() 027ms