Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.116	13 sie 2021, 02:44

	Steps	Scenarios	Features
Login feature	48	1	5	0	0	54	6	1	7	3m 15s 861ms	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 481ms

Then User is successfully logged 029ms

@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" 265ms

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

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

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

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

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

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

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

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

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

And User is successfully logged 027ms

Hooks

After Hooks.rollbackParameters() 102ms

After Hooks.unlockUsers() 089ms

@rollbackParameters @unlockUsers

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 197ms

After Hooks.unlockUsers() 103ms

@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" 217ms

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

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

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

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

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

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

Then Wait "62" seconds 1m 2s

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

And User is successfully logged 029ms

Hooks

After Hooks.rollbackParameters() 183ms

After Hooks.unlockUsers() 090ms

@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" 222ms

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

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" 222ms

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

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

And Close second browser 152ms

And Refresh page 2s 232ms

Then Verify user is logged out 103ms

Hooks

After Hooks.rollbackRemovedAuthorities() 185ms

@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" 215ms

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

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

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

And Close second browser 143ms

And Refresh page 2s 215ms

Then Verify user is logged out 120ms

Hooks

After Hooks.rollbackRemovedAuthorities() 144ms

	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 15s 861ms	Failed

Feature Report