Skip to content

No waits implemented in code so need help #22

@PavanGurram-DevOps

Description

@PavanGurram-DevOps

Hi, Firstly, it is a great code and concept I would say and trying to use it for one of the project where I'm going to create Automation framework from scratch so have few below questions and your inputs will greatly help.

  1. The web application which I'm going to automate is built upon on Angular JS so I believe keeping this code as reference and using the code as it is would work?
  2. How to handle waits properly in Screenplay? I don't see good documentation which explains how to handle waits in code using Screenplay. There is lot documentation for Serenity but not Screenplay I mean.
    a. How to wait until page is loaded?
    b. For example, I want to check element visibility before I perform any action on it so how to do it in efficient way? I have
    used it like below under 'task' but it seems like duplication as I repeated same wait step 3 times as there are 3 target
    locators so wanted to know whether this is the only way or any efficient way to perform waits

public static Performable toISAApplicationForm() {
return Task.where("{0} navigates to Application page",
WaitUntil.the(ImportantInfo.READ_DOCUMENTS,WebElementStateMatchers.isVisible()),
JSClick.on(ImportantInfo.READ_DOCUMENTS),
WaitUntil.the(ImportantInfo.PROCCED_TO_PROCESS_DESCRIPTION,WebElementStateMatchers.isVisible()),
Click.on(ImportantInfo.PROCCED_TO_PROCESS_DESCRIPTION),
WaitUntil.the(Processdescription.START_MY_TRANFER,WebElementStateMatchers.isVisible()),
Click.on(Processdescription.START_MY_TRANFER)
);
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions