Skip to content
← Have an idea? Share it!

Settings and activity

3 results found

  1. Preconditions from called tests should be visible during test execution

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Anonymous supported this idea  · 

  2. Include comments in the PractiTest API

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    waiting for supporters  ·  1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Anonymous supported this idea  · 

  3. Add a way to trigger run machine to start a test set

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Anonymous commented  · 

    Take a look into the "Project - Activity Web Hooks" in the "Integrations" tab of a project's settings. It is capable of making a POST request to a user-provided URL when a test run starts. I used AWS Lambda and AWS API Gateway services to call a custom script; the PractiTest support reps were very helpful with providing me a list of IP addresses that the request could come from so that I could deny access to any other IPs not associated with PractiTest. Hope this helps!