[
https://issues.jboss.org/browse/ARQ-2031?page=com.atlassian.jira.plugin.s...
]
Jessica Streicher commented on ARQ-2031:
----------------------------------------
I did some more testing and it seems to be a matter about an action that is not possible
during the @After execution.
In the failed test i switched the browser to an inner frame in the test method, then i
tried to execute a click on an element that is not available in that frame in the @after
method (the logout button basically, this is executed for all tests).
I assume this messes with the events somehow.
Should executing UI tasks in the @After method be generally avoided or is this a problem
with Arquillian/JUnit/Recorder?
Test method missing in report
-----------------------------
Key: ARQ-2031
URL:
https://issues.jboss.org/browse/ARQ-2031
Project: Arquillian
Issue Type: Bug
Components: Extension - Recorder
Affects Versions: 1.1.10.Final
Environment: Tests are run with Eclipse and JUnit plugin against an external
Webserver (They're pure client UI tests)
Reporter: Jessica Streicher
Whenever a testmethod fails (assertion fail), the test method is not available in the
report.
I have tracked the Problem in the ReportLifecycleObserver class - it is caused because
there are two BeforeTestLifeCycleEvents, but only one AfterTestLifecycleEvent.
The other "passed" test has two AfterTestLifecycleEvents, so an event seems to
be missing when the test "fails"?
I'm afraid my current code cannot be posted publicly, but i'll try to recreate it
later on in another setting. It would still be nice if anyone by chance knows what could
be the cause of this situation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)