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

Refactor test_for.py to use BoaTestConstructor #1157

Merged
merged 1 commit into from Jan 4, 2024
Merged

Conversation

luc10921
Copy link
Collaborator

@luc10921 luc10921 commented Jan 2, 2024

Summary or solution description
Started using BoaTestCase on TestFor

Platform:

  • OS: Windows 11 x64
  • Python version: Python 3.11

@luc10921 luc10921 requested a review from meevee98 January 2, 2024 21:36
@luc10921 luc10921 self-assigned this Jan 2, 2024
@lllwvlvwlll
Copy link
Member

@coveralls
Copy link
Collaborator

coveralls commented Jan 2, 2024

Coverage Status

coverage: 92.1%. remained the same
when pulling 0bd4b85 on CU-86a1hupth
into 73b8da2 on development.

default_folder: str = 'test_sc/for_test'

def test_for_tuple_condition(self):
async def test_for_tuple_condition(self):
Copy link
Collaborator

@meevee98 meevee98 Jan 3, 2024

Choose a reason for hiding this comment

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

Can you break the tests that test both the compilation and execution in two different test cases?
This one for example, into test_for_tuple_condition_compile and test_for_tuple_condition_run

I'm commenting only in this one, but the suggestion is for all test cases that are testing both the compilation and execution

@meevee98 meevee98 merged commit d4c2b92 into development Jan 4, 2024
3 checks passed
@meevee98 meevee98 deleted the CU-86a1hupth branch January 4, 2024 18:56
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

4 participants