-
Notifications
You must be signed in to change notification settings - Fork 119
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
Unit Tests for strings #122
Comments
@harshit496, here is the ticket. I don't know why, i cannot assign the ticket to you. Try to assign yourself. Or maybe you need to message here that I can assign this ticket to you. |
No, even I am not able to self-assign this |
@harshit496 , i've managed |
@aregtech I am including the test in https://github.com/aregtech/areg-sdk/blob/master/tests/units/CMakeLists.txt but it still does seem to compile it. am I missing something? |
@harshit496, where do you work? I can create a branch, merge your changes I'll have a look. |
@harshit496, the branch for you to merge and work. To checkout git fetch origin
git checkout feature/122-unit-tests-for-strings |
@aregtech i haven't created a branch yet. I will add my changes to this branch then |
@aregtech ok nvm I've managed to get it working. Something was wrong with my codespaces setup. Thanks anyways |
@harshit496 , it seems you are very busy. At the moment I remove the ticket assignment in the case if someone else want to continue. I'll assign to you when have more time. |
@aregtech thank you for your patience and apologies for responding late, yes I was swamped with some personal stuff however I am now available to contribute and would love jump back on this issue.Thx. |
Hi @harshit496 , i hope you are fine. |
Motivation.
The string functions are classes are essential, which are used in many cases. It is important to have unit test and very high code coverage of these objects and methods.
Actions
Additional actions
If a bug is found (test failed), there should be a ticket created and the UT code should be included to demonstrate failure.
The text was updated successfully, but these errors were encountered: