Add tests for progress_bar

[HarshKhilawala]

Checklist
Thank you for contributing to QuTiP! Please make sure you have finished the following tasks before opening the PR.

• Please read Contributing to QuTiP Development
• Contributions to qutip should follow the pep8 style.
  You can use pycodestyle to check your code automatically
• Please add tests to cover your changes if applicable.
• If the behavior of the code has changed or new feature has been added, please also update the documentation in the doc folder, and the notebook. Feel free to ask if you are not sure.
• Include the changelog in a file named: doc/changes/<PR number>.<type> 'type' can be one of the following: feature, bugfix, doc, removal, misc, or deprecation (see here for more information).

Description
Add tests for ui.progressbar

[HarshKhilawala]

@Ericgig Can you please guide me through (step-by-step developing test function or test classes) writing tests for progressbar? I don't have much experience with writing python tests? But I am a quick learner and can easily grasp the fundamentals.

[coveralls]

Coverage: 75.391%. Remained the same when pulling a25e4d4 on HarshKhilawala:test-progressbar into 41129bc on qutip:master.

[Ericgig]

You simple need to create a function starting with test_ that use the progress bar. Ideally you would use it in a way that ensure all lines of code are used at least once. Then if there is an error in the code, python will raise an error and the test will fail.

There should be some tutorials for pytest on the web, writing a step per step guide on making tests is more work than making the tests themselves so please have mercy.

[HarshKhilawala]

@Ericgig Thanks for getting back to me. I will refer to pytest tutorials on web but I found some code lines like following:

@pytest.mark.parametrize
@check_pngs_equal
@pytest.fixture
@pytest.mark.repeat(10)...

Can you please let me know when and why were these used? Is there a resource also for this one?

[ajgpitch]

Hello Harsh, Thank for your interest in qutip. The most efficient way for us to interact with code is through Github. Please attempt a draft PR for this. There are many test functions in our project that you can use as a template. Assuming that you are interested in GSoC, when assessing candidates, an ability to work independently is a key criteria. All the best with it, we look forward to reviewing your PR. Alex

…

On Tue, 21 Mar 2023, 18:06 Harsh Khilawala, ***@***.***> wrote: @Ericgig <https://github.com/Ericgig> Thanks for getting back to me. I will refer to pytest tutorials on web but I found some code lines like following: @pytest.mark.parametrize @check_pngs_equal @pytest.fixture @pytest.mark.repeat(10)... Can you please let me know when and why were these used? Is there a resource also for this one? — Reply to this email directly, view it on GitHub <#2127 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACGFP3MUPPBWDTOQGGBNOTLW5HU2ZANCNFSM6AAAAAAV7J6OKU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>