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

Split Arquillian Selenium configuration according to framework

        Details

          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.

            Gliffy Diagrams

              Issue Links

              is related to

              Task - A task that needs to be done. ARQ-369 Selenium and ContextPath injection should be done via ArquillianResource

              • Major - A request that should be considered seriously but is not a show stopper.
              • Closed

                Activity

                Hide
                Permalink
                kpiwko Karel Piwko added a comment -

                Working tree at https://github.com/kpiwko/arquillian/tree/ARQ-329-next

                Show
                kpiwko Karel Piwko added a comment - Working tree at https://github.com/kpiwko/arquillian/tree/ARQ-329-next

                  People

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

                    Dates

                    • Created:
                      Updated:
                      Resolved:

                      Development