[JBoss JIRA] (ARQ-1726) Reporter does not consider screenshots taken manually in test methods
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1726?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1726:
--------------------------------------
Assignee: Stefan Miklosovic
> Reporter does not consider screenshots taken manually in test methods
> ---------------------------------------------------------------------
>
> Key: ARQ-1726
> URL: https://issues.jboss.org/browse/ARQ-1726
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Recorder
> Affects Versions: recorder_1.0.0.Alpha2
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
>
> Beside screenshots taken automatically before / after test method according to configuration, user can take screenshots manually with screenshooter injection like this
> {code}
> @ArquillianResource Screenshooter screenshooter;
> public void test()
> {
> screenshooter.takeScreenshot();
> }
> {code}
> It holds for Recoder injection point as well when user can record videos manually in test method like
> {code}
> @ArquillianResource Recoder recorder;
> public void test()
> {
> recorder.start();
> // something is happening
> recorder.stop();
> }
> {code}
> However, these screenshots and videos does not appear in final report file because when it is taken directly by injection interface, it does not fire any screenshot report event. Logic behind screenshooter and recorder knows this because it invokes screenshooter itself but concrete screenshooter implementation does not fire them.
> There needs to be a way how to report these screenshots which were taken manually as well.
> Taking of screenshots manually is the "last chance" for a user to take them exactly where he needs them to be taken and not showing them in report could be justified however due to user experience these should be taken into account as well definitely.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (ARQ-1744) Provide metadata storage in DroneContext
by Tadeas Kriz (JIRA)
[ https://issues.jboss.org/browse/ARQ-1744?page=com.atlassian.jira.plugin.s... ]
Tadeas Kriz resolved ARQ-1744.
------------------------------
Resolution: Done
> Provide metadata storage in DroneContext
> ----------------------------------------
>
> Key: ARQ-1744
> URL: https://issues.jboss.org/browse/ARQ-1744
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_2.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Tadeas Kriz
> Fix For: drone_2.0.0.Alpha2
>
>
> Other extensions might want to store additional data next to Drone callable/instance and its configuration.
> It would be convenient to expose key:String and value:Object storage for storing metadata directly in DroneContext.
> It is not needed to solve conflict anyhow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (ARQ-1744) Provide metadata storage in DroneContext
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/ARQ-1744?page=com.atlassian.jira.plugin.s... ]
Karel Piwko commented on ARQ-1744:
----------------------------------
Alpha1 was already staged and tested. However, it's very likely there would be an Alpha2 soonish without need to wait.
> Provide metadata storage in DroneContext
> ----------------------------------------
>
> Key: ARQ-1744
> URL: https://issues.jboss.org/browse/ARQ-1744
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_2.0.0.Alpha1
> Reporter: Karel Piwko
> Assignee: Tadeas Kriz
> Fix For: drone_2.0.0.Alpha2
>
>
> Other extensions might want to store additional data next to Drone callable/instance and its configuration.
> It would be convenient to expose key:String and value:Object storage for storing metadata directly in DroneContext.
> It is not needed to solve conflict anyhow.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (ARQ-814) Should support injection of EJBs (as CDI Beans) in Weld Embedded
by Daniel Smith (JIRA)
[ https://issues.jboss.org/browse/ARQ-814?page=com.atlassian.jira.plugin.sy... ]
Daniel Smith commented on ARQ-814:
----------------------------------
I am just realizing I overlooked the pull request and stated the obvious in my last comment. I am still a bit frustrated there has been no update on this issue.
> Should support injection of EJBs (as CDI Beans) in Weld Embedded
> ----------------------------------------------------------------
>
> Key: ARQ-814
> URL: https://issues.jboss.org/browse/ARQ-814
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Weld Containers
> Affects Versions: weld_1.0.0.CR3
> Reporter: Anthony O.
> Assignee: Marko Lukša
> Attachments: EJBTest.java
>
>
> As seen in [this post on the Arquillian forum|https://community.jboss.org/message/723563], we cannot test that simple class as an NPE is thrown from {{org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.MockEjBServices}} which seems to be a copy of Weld code as [Aslak Knutsen|https://community.jboss.org/people/aslak] said.
> {code}
> @RunWith(Arquillian.class)
> public class EJBTest {
> @Deployment
> public static JavaArchive createTestArchive() {
> return ShrinkWrap
> .create(JavaArchive.class, "test.jar")
> .addAsManifestResource(EmptyAsset.INSTANCE, ArchivePaths.create("beans.xml"));
> }
> @Stateless
> public static class SomeService {
> public String someMethod() {
> return "test";
> }
> }
> @Inject
> SomeService someService;
> @Test
> public void testStatelessCall() {
> Assert.assertEquals("test", someService.someMethod());
> }
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (ARQ-1045) Fail fast if path to browser is not valid
by Stefan Miklosovic (JIRA)
[ https://issues.jboss.org/browse/ARQ-1045?page=com.atlassian.jira.plugin.s... ]
Stefan Miklosovic reassigned ARQ-1045:
--------------------------------------
Assignee: Stefan Miklosovic
> Fail fast if path to browser is not valid
> -----------------------------------------
>
> Key: ARQ-1045
> URL: https://issues.jboss.org/browse/ARQ-1045
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_1.1.0.CR2
> Reporter: Karel Piwko
> Assignee: Stefan Miklosovic
> Labels: starter
> Fix For: drone_2.0.0.Alpha2
>
>
> There is no reason to delegate failure to Selenium. If browser binary does not exist for default selenium, simply fail fast. E.g.
> {code:xml}
> <property name="browser">*firefox /opt/firefox-9.0.1/firefox-bin</property>
> {code}
> {code}
> java.lang.RuntimeException: Could not start Selenium session: Failed to start new browser session: java.lang.RuntimeException: Firefox 3 could not be found in the path!
> Please add the directory containing ''firefox.exe'' to your PATH environment
> variable, or explicitly specify a path to Firefox 3 like this:
> *firefox3 c:\blah\firefox.exe
> at com.thoughtworks.selenium.DefaultSelenium.start(DefaultSelenium.java:109)
> at org.jboss.arquillian.drone.selenium.factory.DefaultSeleniumFactory.createInstance(DefaultSeleniumFactory.java:67)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months