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.

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

Create Tests Per Xtext Keywords #139

Closed
16 tasks done
farhan5248 opened this issue May 8, 2024 · 0 comments
Closed
16 tasks done

Create Tests Per Xtext Keywords #139

farhan5248 opened this issue May 8, 2024 · 0 comments
Assignees
Labels
maintenance Used for build/test automation and code clean-up/refactoring

Comments

@farhan5248
Copy link
Owner

farhan5248 commented May 8, 2024

Make new tests for each cucumber feature from Cucumber to AsciiDoctor for all language elements. First make a tree of what needs to be tested

  • CodeToUML
  • UMLToCode
  • UMLToGraph
  • GraphToUML
  • GraphToDocument
  • DocumentToGraph

List of bugs to fix in this work item

  • Background tests need more than one scenario
  • Feature file feature statements aren't mapped
  • Adoc file feature statements, scenario tags, scenario statements, background statements aren't mapped

Make bugs for any language element tests that are missing to be fixed later.

  • Example tables with two rows are mapped incorrectly
  • Example tags and statements are not mapped
  • Example Table column names and Step Table column names are expected to match. This shouldn't be needed.
  • Test out scenario outlines with doc strings
  • Single asterisk in table breaks editor

Maintenance items to make

  • Instead of three tests for lists, just use 1 test with 3 items. Then make 3 unit tests for lists with 1,2,3 items. Do this for all lists of things to keep the feature tests to a minimum
  • All glue code step tables should be the same. Don't have Tag and tags. Either they're all Tag or Tags. All table row specifications should be the same, not like how annotations are different from others. If I paste the feature file for one over another, only the setup docstring, the goal name and the file name should differ.

Tag everything

@farhan5248 farhan5248 self-assigned this May 8, 2024
@farhan5248 farhan5248 added the maintenance Used for build/test automation and code clean-up/refactoring label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Used for build/test automation and code clean-up/refactoring
Projects
None yet
Development

No branches or pull requests

1 participant