Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When a test run ends, Edison should send a callout to tell the website the run has ended - and why #63

Closed
Badgerati opened this issue Mar 5, 2017 · 2 comments
Closed

When a test run ends, Edison should send a callout to tell the website the run has ended - and why #63

Badgerati opened this issue Mar 5, 2017 · 2 comments
Assignees
@Badgerati
Labels
engine feature
Milestone
v1.5.0

Comments

@Badgerati
Copy link
Owner

Badgerati commented Mar 5, 2017 •
edited

Much like issue #62, this one will be for Edison to send a callout when a test run has ended - using the SessionId from the start callout.

The data sent from Edison should be the:

  • SessionId
  • DateTime the run ended
  • Reason the run ended (could be naturally, forced or crashed)

Note, that if the SessionId is not available, just send the TestRunId and TestRunName instead.
@Badgerati Badgerati mentioned this issue Mar 5, 2017
Closed
@Badgerati Badgerati modified the milestone: v1.5.0 Mar 6, 2017
@Badgerati Badgerati self-assigned this Mar 13, 2017
@Badgerati
Copy link
Owner Author

The callout for the End action will just notify an endpoint the run has ended, the reason, for now, will be left out.

Badgerati added a commit that referenced this issue Mar 13, 2017
@Badgerati
Resolves #63: Send out an end event if using TestResultUrl
41b1da3
Badgerati added a commit that referenced this issue Mar 13, 2017
@Badgerati
Merge pull request #74 from Badgerati/Issue-63
5014627 
Resolves #63: Send out an end event if using TestResultUrl
@Badgerati
Copy link
Owner Author

Merged into Epic branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Badgerati Badgerati

Labels
engine feature
Projects
None yet
Milestone
v1.5.0
Development

No branches or pull requests
1 participant
@Badgerati