-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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.
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
[Endpoint] TEST: GET alert details - boundary test for first alert retrieval #60320
Conversation
Pinging @elastic/endpoint-response (Team:Endpoint Response) |
Pinging @elastic/endpoint-app-team (Feature:Endpoint) |
@@ -27,7 +27,7 @@ export default function({ getService }: FtrProviderContext) { | |||
const nextPrevPrefixPageSize = 'page_size=10'; | |||
const nextPrevPrefix = `${nextPrevPrefixQuery}&${nextPrevPrefixDateRange}&${nextPrevPrefixSort}&${nextPrevPrefixOrder}&${nextPrevPrefixPageSize}`; | |||
|
|||
describe('Endpoint alert API', () => { | |||
describe.only('Endpoint alert API', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't forget to remove the only
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yah, i thought it would have been caught in linting before the commit was successful, how did that even happen?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pushed it up righter, now. i think i mis-understood the git processing I did... it didn't push the latest change after the commit passed, I see the mistake now tho I don't truly 'get' git in this regard, lol. thanks P.
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
…trieval (elastic#60320) * boundary test for first alert retrieval * boundary test for first alert retrieval cleaned up * redo merge conflict resolving for api test * redo merge conflict resolving for api test try 2 * updating to current dataset expectations Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
…trieval (#60320) (#60718) * boundary test for first alert retrieval * boundary test for first alert retrieval cleaned up * redo merge conflict resolving for api test * redo merge conflict resolving for api test try 2 * updating to current dataset expectations Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
…o alerting/tls-warning * 'alerting/tls-warning' of github.com:gmmorris/kibana: (32 commits) [ML] Listing all categorization wizard checks (elastic#60502) [Upgrade Assistant] First iteration of batch reindex docs (elastic#59887) [SIEM] Export timeline (elastic#58368) [SIEM] Add support for actions and throttle in Rules (elastic#59641) Fix ace a11y listener (elastic#60639) Add addInfo toast to core notifications service (elastic#60574) fix test description (elastic#60638) [SIEM] Cypress screenshots upload to google cloud (elastic#60556) [canvas/shareable_runtime] sync sass loaders with kbn/optimizer (elastic#60653) [SIEM] Fixes Modification of ML Rules (elastic#60662) [SIEM] [Case] Bulk status update, add comment avatar, id => title in breadcrumbs (elastic#60410) [Alerting] add functional tests for index threshold alertType (elastic#60597) [Ingest]EMT-248: add post action request handler and resources (elastic#60581) Return incident's url (elastic#60617) [Endpoint] TEST: GET alert details - boundary test for first alert retrieval (elastic#60320) [ML] Transforms: Fix pivot preview table mapping. (elastic#60609) [Endpoint] Log random seed for sample data CLI to console (elastic#60646) Use common event model for determining if event is v0 or v1 (elastic#60667) Disables PR Project Assigner workflow [Reporting] Allow reports to be deleted in Management > Kibana > Reporting (elastic#60077) ...
Summary
copy of an existing api test which was GET'ing and asserting against the last alert in the index. This tests the first, and therefore we can assert against the 'prev' link is null and and that the 'next' alert is some valid id.
Testrail case was added for this new api test:
https://elastic.testrail.io/index.php?/cases/view/655
Checklist
n/a
For maintainers
n/a