Skip to content

Forecasting features#7

Open
AlexanderYenGEV wants to merge 10 commits intotrolie:mainfrom
AlexanderYenGEV:forecasting-features
Open

Forecasting features#7
AlexanderYenGEV wants to merge 10 commits intotrolie:mainfrom
AlexanderYenGEV:forecasting-features

Conversation

@AlexanderYenGEV
Copy link
Collaborator

Added new scenarios to primarily snapshot_filters and snaphshot_formats.
Added a clearer terminal output for tests.

@AlexanderYenGEV
Copy link
Collaborator Author

Theres alot of files changed so sorry about that. For future PR, I will be keeping the changes to be alot smaller scaled so it is easier to review. But these are the main changes to the tests that I have been working on so far.

Copy link
Contributor

@caindy caindy left a comment

Choose a reason for hiding this comment

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

Let's get your other PR merged then rebase this. Please address the comments I've made so far, and I will circle back and review the rest.

# PATCH Submit a Forecast Proposal
Scenario Outline: Submit a forecast proposal
Given the Content-type header is set to `<response_type>`
And the body is loaded from `<file_name>`
Copy link
Contributor

@caindy caindy Jul 30, 2025

Choose a reason for hiding this comment

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

I'd suggest creating multiple scenarios and changing the language here to say

Suggested change
And the body is loaded from `<file_name>`
And the request body is a valid `<content_type>` for the authenticated Ratings Provider

For now, we can implement the step definition to switch on <content_type> and load the appropriate file.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Could you clarify on what you mean by multiple scenarios? Wouldn't submitting forecast proposal just encompass a singular scenario.

Copy link
Contributor

Choose a reason for hiding this comment

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

Apologies, when I first started that comment I was thinking it would be cleaner to have a Submit slim forecast proposal, Submit standard forecast proposal, etc., but I thought better of it (it was late). I will edit my comment to remove "multiple scenarios".

Rebasing, resolved conflict in gitignore and conftest.py

Rebasing, resolved conflict in gitignore and conftest.
Resolved 2nd conflic in gitignore and conftest.py for rebase
@AlexanderYenGEV AlexanderYenGEV requested a review from caindy July 31, 2025 18:39
Signed-off-by: AlexanderYenGEV <Alexander.Yen@gevernova.com>
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.

3 participants