Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.125	20 sie 2021, 05:38

	Steps	Scenarios	Features
Login feature	48	1	5	0	0	54	6	1	7	3m 16s 632ms	Failed

Scenario Outline Verify that user is able to login using valid login and password

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" 15s 434ms

Then User is successfully logged 030ms

@rollbackParameters @unlockUsers

Scenario Outline Checking if setting for blocking the user after X failed attempts works correctly [A-7287]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 234ms

And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "3" 106ms

Given Failed login as "neuca-admin" 1s 479ms

Then Verify that login error reason is "auth.invalidLoginOrPassword" 464ms

Given Failed login as "neuca-admin" 1s 335ms

Then Verify that login error reason is "auth.invalidLoginOrPassword" 413ms

Then Login as "neuca-admin" 2s 147ms

Given Failed login as "neuca-admin" 1s 362ms

Then Verify that login error reason is "auth.invalidLoginOrPassword" 440ms

Then Login as "neuca-admin" 2s 018ms

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 098ms

After Hooks.unlockUsers() 142ms

@rollbackParameters @unlockUsers

Scenario Outline Check if blocking of user will end after a lockout time [A-7288]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-sempertrans" 239ms

And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 102ms

And Prepare parameter "BLOCKED_USER_DURATION_IN_MINUTES" with value: "1" 105ms

When Failed login as "sempertrans-admin" 1s 420ms

And Verify that login error reason is "auth.invalidLoginOrPassword" 519ms

And Failed login as "sempertrans-admin" 1s 251ms

And Verify that login error reason is "auth.accountLocked" 285ms

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 7s 411ms

And User is successfully logged 026ms

Hooks

After Hooks.rollbackParameters() 205ms

After Hooks.unlockUsers() 084ms

@rollbackParameters @unlockUsers

Scenario Outline Check if blocking of user will end after a lockout time [A-7288]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 225ms

And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 090ms

And Prepare parameter "BLOCKED_USER_DURATION_IN_MINUTES" with value: "1" 109ms

When Failed login as "adama-admin" 1s 341ms

And Verify that login error reason is "auth.invalidLoginOrPassword" 509ms

And Failed login as "adama-admin" 1s 341ms

And Verify that login error reason is "auth.accountLocked" 235ms

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 6s 154ms

And User is successfully logged 030ms

Hooks

After Hooks.rollbackParameters() 192ms

After Hooks.unlockUsers() 092ms

@rollbackRemovedAuthorities

Scenario Outline Check if user is logged out when another person login on same account

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 223ms

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "bausch-admin" 026ms

Error message

javax.persistence.NonUniqueResultException: query did not return a unique result: 4
	at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:123)
	at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:157)
	at org.hibernate.query.internal.AbstractProducedQuery.getSingleResult(AbstractProducedQuery.java:1562)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getBigIntegerResult(ApolloSelectDbService.java:117)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.findPersonRoleGroup(ApolloSelectDbService.java:171)
	at CucumberTests.Utils.AuthorityTest.removeBasicAuthoritiesToUser(AuthorityTest.java:63)
	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

Hooks

After Hooks.rollbackRemovedAuthorities() 000ms

@rollbackRemovedAuthorities

Scenario Outline Check if user is logged out when another person login on same account

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 235ms

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "farmacol-admin" 225ms

And Login as "farmacol-admin" 6s 374ms

And Login as "farmacol-admin" on another browser 3s 909ms

And Close second browser 161ms

And Refresh page 2s 236ms

Then Verify user is logged out 094ms

Hooks

After Hooks.rollbackRemovedAuthorities() 201ms

@rollbackRemovedAuthorities

Scenario Outline Check if user is logged out when another person login on same account

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 229ms

And Remove basic authorities "ROLE_ALLOW_CONCURRENT_SESSIONS" from user "alrec-admin" 186ms

And Login as "alrec-admin" 5s 873ms

And Login as "alrec-admin" on another browser 3s 471ms

And Close second browser 150ms

And Refresh page 2s 223ms

Then Verify user is logged out 112ms

Hooks

After Hooks.rollbackRemovedAuthorities() 148ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Login feature	48	1	5	0	0	54	6	1	7	3m 16s 632ms	Failed

Feature Report