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

Add history graph use case in e2e tests #514

Merged

Conversation

keisuke-umezawa
Copy link
Member

@keisuke-umezawa keisuke-umezawa commented Jul 2, 2023

Contributor License Agreement

This repository (optuna-dashboard) and Goptuna share common code.
This pull request may therefore be ported to Goptuna.
Make sure that you understand the consequences concerning licenses and check the box below if you accept the term before creating this pull request.

  • I agree this patch may be ported to Goptuna by other Goptuna contributors.

Reference Issues/PRs

What does this implement/fix? Explain your changes.

Copy link
Member

@c-bata c-bata left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

However, I'd like to share some concerns. The current approach to write e2e_tests could lead to potential issues as the number of test cases increases. We need to create multiple studies within conftest.py for each test case although this test case only require the first study. So that it could substantially increases the time for running tests.

Moreover, I have a maintainability concern. If each test needs to assert more detailed conditions, it heavily depends on studies, set up in conftest.py. It makes tests complex. Ideally, it would be better to prepare only the minimum necessary studies for each test case.

@keisuke-umezawa
Copy link
Member Author

@c-bata
Thank you for the feedback! I will think about better solutions.

@keisuke-umezawa keisuke-umezawa merged commit f159b4f into optuna:main Jul 9, 2023
9 checks passed
@keisuke-umezawa keisuke-umezawa deleted the feature/e2e-usecase-history branch July 9, 2023 06:55
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

Successfully merging this pull request may close these issues.

None yet

2 participants