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

[SPIKE] How do we parameterize node based functional tests to expand with changing functionality #10328

Open
Tracked by #9649
QMalcolm opened this issue Jun 18, 2024 · 0 comments
Assignees

Comments

@QMalcolm
Copy link
Contributor

QMalcolm commented Jun 18, 2024

Description

We want to ensure we automatically test all node types which are supposed to work with specific. We've discussed a few possible ways to identify what nodes a feature should support, but haven't gamed them out and gotten buy in:

  • Using GraphNode
  • Declaring an explicit enum per feature (similar to Retry work)
  • Using properties on nodes to determine what features they should support
  • Maybe others?

Once we've come up with a path forward, we can begin writing parameterized functional tests which test a feature with every node type it is supposed to support.

Acceptance Criteria

  • We've decided on a way to identify what node types a feature should support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant