Cucumber-JVM Reports - Feature: Login feature

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.58	13 sie 2021, 02:50

	Steps	Scenarios	Features
Login feature	48	1	5	0	0	54	6	1	7	2m 29s 281ms	Failed

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" 3s 047ms

Then User is successfully logged 003ms

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

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

Given Failed login as "neuca-admin" 496ms

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

Given Failed login as "neuca-admin" 503ms

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

Then Login as "neuca-admin" 911ms

Given Failed login as "neuca-admin" 494ms

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

Then Login as "neuca-admin" 922ms

And User is successfully logged 004ms

Hooks

After Hooks.rollbackParameters() 014ms

After Hooks.unlockUsers() 023ms

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

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

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

When Failed login as "sempertrans-admin" 519ms

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

And Failed login as "sempertrans-admin" 531ms

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

Then Wait "62" seconds 1m 2s

And Login as "sempertrans-admin" 1s 857ms

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 045ms

After Hooks.unlockUsers() 017ms

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

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

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

When Failed login as "adama-admin" 501ms

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

And Failed login as "adama-admin" 491ms

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

Then Wait "62" seconds 1m 2s

And Login as "adama-admin" 1s 621ms

And User is successfully logged 005ms

Hooks

After Hooks.rollbackParameters() 029ms

After Hooks.unlockUsers() 013ms

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

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

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

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

And Login as "farmacol-admin" 1s 532ms

And Login as "farmacol-admin" on another browser 1s 916ms

And Close second browser 130ms

And Refresh page 2s 148ms

Then Verify user is logged out 032ms

Hooks

After Hooks.rollbackRemovedAuthorities() 026ms

@rollbackRemovedAuthorities

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Login as "alrec-admin" 1s 537ms

And Login as "alrec-admin" on another browser 1s 810ms

And Close second browser 074ms

And Refresh page 2s 142ms

Then Verify user is logged out 028ms

Hooks

After Hooks.rollbackRemovedAuthorities() 025ms

	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	2m 29s 281ms	Failed

Feature Report