Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-371

Split Arquillian Selenium configuration according to framework

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 1.0.0.Alpha5
    • None
    • Extension - Drone
    • None

    Description

      There is no reason to have bloated configuration api...instead provide a way how each instantiator retrieves its own configuration which is tailored...e.g. no concept of wait types for ordinary Selenium, but they are needed for Ajocado.

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. ARQ-369 Selenium and ContextPath injection should be done via ArquillianResource

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              kpiwko Karel Piwko
              kpiwko Karel Piwko
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: