Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Utilize test data from `aas-core3.0-testgen` rather than our proprietary set.

Open
  • Is something wrong?
#109 2 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

@hpoeche is already working on this.

Since Aug 1, 2026.

  • #608 by @hpoeche — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Start by reviewing linked pull request #608 and locating the current testing pipeline and proprietary test-data integration. Replace that source with regularly fetched aas-core3.0-testgen data, run the comprehensive validation suite, and remove the proprietary set only after gaps and inconsistencies are resolved.

Written by the indexing model from the issue text.

Description

enhancement sdk

Issue:
We've been using our proprietary test set for validating the SDK against the metamodel. However, with every change in the metamodel that necessitates an update to our SDK, we find ourselves having to make corresponding adjustments to our test data. This iterative process is resource-intensive and can lead to potential inconsistencies and oversights.

Proposal:
To streamline this process and ensure a more robust testing framework, we recommend transitioning to the test data provided by aas-core3.0-testgen. Here are the key benefits of making this switch:

  1. Comprehensive Coverage: The aas-core3.0-testgen provides an extensive set of test data, ensuring thorough validation of our SDK against a wide range of scenarios.

  2. Automatic Generation: The test data from aas-core3.0-testgen is automatically generated, which means we'll always have the most up-to-date test cases without the manual effort of creating or updating them.

  3. Reduced Maintenance: By relying on this external test set, we can significantly reduce the overhead associated with maintaining our own test data. This will allow our team to focus on enhancing the SDK and addressing other critical priorities.

  4. Consistency with the Community: Adopting a widely-used test set ensures that our SDK is in alignment with community standards and best practices.

Next Steps:
We should initiate a transition plan to integrate aas-core3.0-testgen test data into our testing pipeline. This will involve:

  • Setting up a mechanism to regularly fetch the latest test data from aas-core3.0-testgen.
  • Adapting our testing infrastructure to utilize this new data source.
  • Conducting an initial comprehensive test run to identify any gaps or inconsistencies.
  • Decommissioning our proprietary test set once the transition is complete and verified.
Dominant language
Python
Stars
104
Forks
56
Avg merge
12d 13h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-basyx/basyx-python-sdk

All issues in eclipse-basyx/basyx-python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.