Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

fix: use proper gherkin comments #519

Merged
merged 1 commit into from
Dec 2, 2020

Conversation

mdelapenya
Copy link
Contributor

What does this PR do?

It uses proper Gherkin syntax for comments

Why is it important?

The feature file cannot be parsed, failing the build

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have run the Unit tests for the CLI, and they are passing locally
  • I have run the End-2-End tests for the suite I'm working on, and they are passing locally
  • I have noticed new Go dependencies (run make notice in the proper directory)

Related issues

@mdelapenya mdelapenya self-assigned this Dec 2, 2020
@mdelapenya mdelapenya requested review from a team and EricDavisX December 2, 2020 17:20
@mdelapenya mdelapenya added the bug Something isn't working label Dec 2, 2020
@mdelapenya mdelapenya marked this pull request as ready for review December 2, 2020 17:21
@mdelapenya
Copy link
Contributor Author

Merging as the parser works again. Thanks!

@mdelapenya mdelapenya merged commit 3fc7bdd into elastic:master Dec 2, 2020
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #519 opened

  • Start Time: 2020-12-02T17:20:26.777+0000

  • Duration: 22 min 7 sec

Test stats 🧪

Test Results
Failed 0
Passed 33
Skipped 12
Total 45

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 33
Skipped 12
Total 45

@EricDavisX
Copy link
Contributor

thanks - yes, i misread the proper Gherkin comment format, and used Golang and merged it before someone more experienced could review. bad process and i should be more careful in the future. thanks for the help in cleaning it up.

@mdelapenya mdelapenya deleted the fix-gherkin branch December 2, 2020 18:04
mdelapenya added a commit to mdelapenya/e2e-testing that referenced this pull request Dec 2, 2020
mdelapenya added a commit to mdelapenya/e2e-testing that referenced this pull request Dec 2, 2020
This was referenced Dec 2, 2020
mdelapenya added a commit that referenced this pull request Dec 2, 2020
* work for issue #379 - adding back rpm and deb tests (#439)

* adding back rpm and deb tests

* arbitrary change to trigger ci tests

* fix linting

* fixing more linting

* fully exploring gherkin linting apparently

* final linting fix

* updating ci suites to match new tags

* reset indention w feedback passes linting locally

* adding skip support and skipping rpm and deb tests

* back to fixing linting for tags now

Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>

* fix: use proper gherkin comments (#519)

Co-authored-by: Eric Davis <eric.davis@elastic.co>
mdelapenya added a commit that referenced this pull request Dec 2, 2020
* work for issue #379 - adding back rpm and deb tests (#439)

* adding back rpm and deb tests

* arbitrary change to trigger ci tests

* fix linting

* fixing more linting

* fully exploring gherkin linting apparently

* final linting fix

* updating ci suites to match new tags

* reset indention w feedback passes linting locally

* adding skip support and skipping rpm and deb tests

* back to fixing linting for tags now

Co-authored-by: Manuel de la Peña <mdelapenya@gmail.com>

* fix: use proper gherkin comments (#519)

Co-authored-by: Eric Davis <eric.davis@elastic.co>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants