MarketSquare / MarketSquare/robotframework-stacktrace
The test suite is failing
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Python
- Estrellas
- 18
- Forks
- 2
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Hi,
Perhaps I'm doing something wrong, but here's what I get when running python -m robot tests on the latest 0.4.1 release (archive from PyPI):
starting phase `check'
==============================================================================
Tests
==============================================================================
Tests.A-Suite
==============================================================================
Tests.A-Suite.B-Suite
==============================================================================
Tests.A-Suite.B-Suite.C-Suite
==============================================================================
Tests.A-Suite.B-Suite.C-Suite.D-Suite
==============================================================================
first teardown fail | FAIL |
Teardown failed:
by purpose
------------------------------------------------------------------------------
Second setup fails | FAIL |
Setup failed:
'False' should be true.
Also teardown failed:
this fails as well
------------------------------------------------------------------------------
Tests.A-Suite.B-Suite.C-Suite.D-Suite | FAIL |
Suite teardown failed:
'False' should be true.
2 tests, 0 passed, 2 failed
==============================================================================
Tests.A-Suite.B-Suite.C-Suite | FAIL |
2 tests, 0 passed, 2 failed
==============================================================================
Tests.A-Suite.B-Suite.C2-Suite
==============================================================================
Tests.A-Suite.B-Suite.C2-Suite.Never Runs
==============================================================================
Hi | FAIL |
Parent suite setup failed:
This is a Suite Setup
------------------------------------------------------------------------------
Tests.A-Suite.B-Suite.C2-Suite.Never Runs | FAIL |
Parent suite setup failed:
This is a Suite Setup
1 test, 0 passed, 1 failed
==============================================================================
Tests.A-Suite.B-Suite.C2-Suite | FAIL |
Suite setup failed:
This is a Suite Setup
Also suite teardown failed:
Here the teardow
1 test, 0 passed, 1 failed
==============================================================================
Tests.A-Suite.B-Suite.C3-Suite
==============================================================================
Tests.A-Suite.B-Suite.C3-Suite.Fails Suite Teardown
==============================================================================
Test | PASS |
------------------------------------------------------------------------------
Tests.A-Suite.B-Suite.C3-Suite.Fails Suite Teardown | FAIL |
Suite teardown failed:
in Suite Teardown
1 test, 0 passed, 1 failed
==============================================================================
Tests.A-Suite.B-Suite.C3-Suite | FAIL |
1 test, 0 passed, 1 failed
==============================================================================
Tests.A-Suite.B-Suite | FAIL |
Suite teardown failed:
This Fails as well....
4 tests, 0 passed, 4 failed
==============================================================================
Tests.A-Suite | FAIL |
4 tests, 0 passed, 4 failed
==============================================================================
[ ERROR ] Error in file '/tmp/guix-build-python-robotframework-stacktrace-0.4.1.drv-0/robotframework-stacktrace-0.4.1/tests/basics.robot' on line 4: Resource file 'keywords.resource' does not exist.
Tests.Basics
==============================================================================
PASS Testing 1 | PASS |
------------------------------------------------------------------------------
Testing 1 | FAIL |
1 != 2
------------------------------------------------------------------------------
Testing 2 | FAIL |
No keyword with name 'Keyword2' found. Did you mean:
Keyword
BuiltIn.Run Keyword
------------------------------------------------------------------------------
Resolve Variable | FAIL |
scalar content
------------------------------------------------------------------------------
Fail with a List | FAIL |
Lists are different:
Index 2: three != 3
------------------------------------------------------------------------------
Fail with dict | FAIL |
Dictionary does not contain key 'key'.
------------------------------------------------------------------------------
Fail expanded keys | FAIL |
Keyword 'Fail Expanded' got unexpected named arguments 'key1' and 'key2'.
------------------------------------------------------------------------------
Fail expanded items | FAIL |
['key1', 'key2']
------------------------------------------------------------------------------
Fail expanded list | FAIL |
['one', 'two', 'three']
------------------------------------------------------------------------------
Fail with large file | FAIL |
This file is full of vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit
vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit
vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit v...
[ Message content over the limit has been removed. ]
...mit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit
vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit vomit
!= puke
------------------------------------------------------------------------------
Fail with number | FAIL |
1775675 != 23
------------------------------------------------------------------------------
Fails with Unknown Variable | FAIL |
Variable '${unknown_var}' not found.
------------------------------------------------------------------------------
Fail a compount | FAIL |
this is a scalar content text with a ['one', 'two', 'three']
------------------------------------------------------------------------------
Wrong If | FAIL |
Evaluating expression 'time.seven' failed: AttributeError: module 'time' has no attribute 'seven'
------------------------------------------------------------------------------
Tests.Basics | FAIL |
14 tests, 1 passed, 13 failed
==============================================================================
Tests.RunKeywords and WUKS
==============================================================================
Tests.RunKeywords and WUKS.Run Keywords WUKS
==============================================================================
Run Keyword | FAIL |
This one fails
------------------------------------------------------------------------------
Run Keyword And Ignore Error | PASS |
------------------------------------------------------------------------------
Run Keyword And Continue On Failure | FAIL |
Several failures occurred:
1) 1st Error
2) 2nd Error
3) 3rd Error
4) 4th Error
5) 5th Error
------------------------------------------------------------------------------
Run Keyword And Expect Error | PASS |
------------------------------------------------------------------------------
Run Keyword And Return | FAIL |
Evaluating expression '" ".join(None)' failed: TypeError: can only join an iterable
------------------------------------------------------------------------------
Run Keyword And Return If | FAIL |
Evaluating expression '" ".join(None)' failed: TypeError: can only join an iterable
------------------------------------------------------------------------------
Run Keyword And Return Status | FAIL |
'False' should be true.
------------------------------------------------------------------------------
Run Keyword And Warn On Failure [ WARN ] Executing keyword 'Top Level One' failed:
This should basically be a warning
| PASS |
------------------------------------------------------------------------------
Run Keywords | FAIL |
with a message
------------------------------------------------------------------------------
Pass WUKS | PASS |
------------------------------------------------------------------------------
Fail in WUKS | FAIL |
Keyword 'Fails some times' failed after retrying 9 times. The last error was: 10 != 9
------------------------------------------------------------------------------
Tests.RunKeywords and WUKS.Run Keywords WUKS | FAIL |
11 tests, 4 passed, 7 failed
==============================================================================
Tests.RunKeywords and WUKS | FAIL |
11 tests, 4 passed, 7 failed
==============================================================================
Tests.Side-Effecting
==============================================================================
Side effect in variable resolving | PASS |
------------------------------------------------------------------------------
Side effect in variable resolving FAILING | FAIL |
a
------------------------------------------------------------------------------
Tests.Side-Effecting | FAIL |
2 tests, 1 passed, 1 failed
==============================================================================
Tests | FAIL |
31 tests, 6 passed, 25 failed
==============================================================================
Output: /tmp/guix-build-python-robotframework-stacktrace-0.4.1.drv-0/robotframework-stacktrace-0.4.1/output.xml
Log: /tmp/guix-build-python-robotframework-stacktrace-0.4.1.drv-0/robotframework-stacktrace-0.4.1/log.html
Report: /tmp/guix-build-python-robotframework-stacktrace-0.4.1.drv-0/robotframework-stacktrace-0.4.1/report.html
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "python" arguments: ("-m" "robot" "tests") exit-status: 25 term-signal: #f stop-signal: #f>
phase `check' failed after 0.5 seconds
command "python" "-m" "robot" "tests" failed with status 25
Ideas?
The only direct dependencies are python-robotframework@4.1.2 and python@3.9.6.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Reproduce el informe con python -m robot tests usando la versión 0.4.1. Empieza por el directorio tests y el error en tests/basics.robot sobre la ausencia del archivo keywords.resource; después, investiga los fallos de setup, teardown y de las pruebas indicados. Se considera terminado cuando la suite de pruebas se ejecuta sin estos fallos indicados.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- testing-qa
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 20/100