codeceptjs / codeceptjs/CodeceptJS

AutoLogin Check() operation is failing

Aberta
#2,811 0 comentários 0 reações 0 responsáveis Ver no GitHub
Linguagem predominante
JavaScript
Estrelas
4.2k
Forks
757
Merge médio
2d 9h
PRs com merge (30d)
16

Descrição

#### What are you trying to achieve?
I am trying to use the AutoLogin feature to run multiple tests.

#### What do you get instead?

On the Second test it's failing to preform the check() operation and throwing connection issue as shown below-

Test 2
» [Window Size] [object Object]
[1] Starting session
I am on page "/"
I set cookie [{"domain":".github.com","expiry":1645006954,"httpOnly":true,"name":"dotcom_user","path":"/","sameSite":"Lax","secure":true,"value":"KKTestUser"},{"domain":"github.com","httpOnly":true,"name":"_gh_sess","path":"/","s...
[1] < check login > Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] < check login > Error | unknown error: java.net.ConnectException: Connection refused: connect
» Failed auto login for TestFeature due to unknown error: java.net.ConnectException: Connection refused: connect
» Logging in again
[1] < check login > Starting session
I: login
I am on page "/login"
[1] < auto login > Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] < auto login > Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] < auto login > Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] < auto login > Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] < auto login > Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] < auto login > Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] < auto login > Finalize session
[1] Finalize < check login > session
[1] Starting < teardown > session
[1] < teardown > Finalize < check login > session
» < screenshotOnFail > Test failed, try to save a screenshot
» Screenshot has been saved to C:\.\.\.\.\output\TestFeature_be_1613470980.failed.png
» < unknown error: java.net.ConnectException: Connection refused: connect >
× FAILED in 20129ms

I see element "#dashboard-repos-filter-left"
[1] Retrying... Attempt #2
[1] Retrying... Attempt #3
[1] Retrying... Attempt #4
[1] Retrying... Attempt #5
[1] Retrying... Attempt #6
[1] Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] Error | unknown error: java.net.ConnectException: Connection refused: connect
[1] Starting < teardown > session
[1] < teardown > Stopping recording promises
» < screenshotOnFail > Test failed, try to save a screenshot
» Screenshot has been saved to C:\.\.\.\.\output\Validate_C_1613471041.failed.png
» < unknown error: java.net.ConnectException: Connection refused: connect >
× FAILED in 69085ms

[2] Starting recording promises
[2] Error | invalid session id: No active session with ID 391b802f8b59b3085111b0ff6fb98ba7
invalid session id: No active session with ID 391b802f8b59b3085111b0ff6fb98ba7

-- FAILURES:

1) TestFeature
"before each" hook: Before in "TestFeature":
done() called multiple times in hook of file C:\.\.\.\.\TestFeature_test.js; in addition, done() received error: unknown error: java.net.ConnectException: Connection refused: connect
at Object.getErrorFromResponseBody (C:\.\.\.\.\node_modules\webdriver\build\utils.js:189:12)
at WebDriverRequest._request (C:\.\.\.\.\node_modules\webdriver\build\request.js:168:31)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Browser.wrapCommandFn (C:\.\.\.\.\node_modules\@wdio\utils\build\shim.js:79:29)
at async Browser.wrapCommandFn (C:\.\.\.\.\node_modules\@wdio\utils\build\shim.js:79:29)
at async loginAndSave (C:\.\.\.\.\node_modules\codeceptjs\lib\plugin\autoLogin.js:255:23)
Error: done() called multiple times in hook of file C:\.\.\.\.\TestFeature_test.js; in addition, done() received error: unknown error: java.net.ConnectException: Connection refused: connect
at Object.getErrorFromResponseBody (node_modules\webdriver\build\utils.js:189:12)
at WebDriverRequest._request (node_modules\webdriver\build\request.js:168:31)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Browser.wrapCommandFn (node_modules\@wdio\utils\build\shim.js:79:29)
at async Browser.wrapCommandFn (node_modules\@wdio\utils\build\shim.js:79:29)
at async loginAndSave (node_modules\codeceptjs\lib\plugin\autoLogin.js:255:23)
at C:\.\.\.\.\node_modules\codeceptjs\lib\scenario.js:117:26
at processTicksAndRejections (internal/process/task_queues.js:93:5)

2) TestFeature
Test 2:
java.net.ConnectException: Connection refused: connect
at Object.getErrorFromResponseBody (node_modules\webdriver\build\utils.js:189:12)
at WebDriverRequest._request (node_modules\webdriver\build\request.js:168:31)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Browser.wrapCommandFn (node_modules\@wdio\utils\build\shim.js:79:29)
at async Browser.$$ (node_modules\webdriverio\build\commands\browser\$$.js:53:17)
at async Browser.wrapCommandFn (node_modules\@wdio\utils\build\shim.js:79:29)
at async WebDriver._locate (node_modules\codeceptjs\lib\helper\WebDriver.js:758:19)
at async WebDriver.seeElement (node_modules\codeceptjs\lib\helper\WebDriver.js:1314:17)

### Details

* CodeceptJS version: 3.0.5
* NodeJS Version: 14.15.0
* Operating System: Windows 10
* webdriverio 7.0.1

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

Leia node_modules/codeceptjs/lib/plugin/autoLogin.js nas proximidades de loginAndSave e do hook com falha de TestFeature_test.js; reproduza a execução de AutoLogin do segundo teste com as versões listadas de CodeceptJS, Node.js e webdriverio. Está concluído quando o caminho repetido de check() não produzir mais falhas connection-refused ou invalid-session e o teste for concluído sem chamadas duplicadas a done().

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
javascript, nodejs
Domínio
testing-qa
Tipo de issue
Bug
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Estagnada
Clareza
Precisa de esclarecimento
Facilidade para iniciantes
25/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.