-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Write more unit tests & add code coverage tests #1567
Comments
If someone has ideas for automating GUI tests with Qt, please add some comments! |
We can use Squish |
@chinmay7016 - Squish is a commercial product - last I checked it was US$7,000 per year. |
What can I refer to understand the testing framework so that I can write more unit test? |
Selenium?? |
Hi Sir! I researched a bit for some softwares based upon what companies are currently using and cost as well, we can use any one out of Playwright or Katalon Studio. As both are open are source but as it is testing at an advanced level we might have to purchase for some addition features. Both are really good and well-known but KATALON IS CHEAPER, so i would suggest using that more. But i suggested Playwright as well because it sometimes depends which testing software is more compatible with our device which reduces hassle after implementation. So, i gave an alternative for Katalon Studios as well. |
We're not going to rely on a commercial product for testing. It needs to be deployable at scale. |
Expanding unit test coverage is crucial, and I'm considering tackling this task once the blur feature is added. Are there any plans to incorporate visual testing in the future? |
We actually already have several visual tests through |
BTW, adding coverage to We'd just want a GitHub action that uses |
Handling the GUI for testing is tricky, but as seen in #1564 there are issues in the
core
andio
modules that need more unit testing.Since there are tools to help generate tests for methods, it would be great to expand the unit tests and improve coverage.
I'm marking this as a good first issue, since the test framework is already set up and there are many unit tests already.
The text was updated successfully, but these errors were encountered: