-
Notifications
You must be signed in to change notification settings - Fork 193
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
[Bug]: displaying "~value into varible" instead of "~value into variable" #244
Comments
@creek23 Thanks for raising this. I see that you are willing to provide a fix for this. |
+Amit Savyasachi ***@***.***>
Regards,
Rukmangada(KR)
Founder & CEO | Testsigma
https://testsigma.com
<https://mailtrack.io/trace/link/bd365f45991e8c30b9f3e8a688c275625e9eefb8?url=https%3A%2F%2Ftestsigma.com%2F&userId=4655759&signature=498641d6e017a0a6>
…On Wed, Dec 21, 2022 at 11:08 AM Tarunava ***@***.***> wrote:
@creek23 <https://github.com/creek23> Thanks for raising this. I see that
you are willing to provide a fix for this.
Please raise a pull request for this issue in order to merge to dev
branch. Let us know in case of any issues.
—
Reply to this email directly, view it on GitHub
<#244 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVOCK6XYDMSRBUXKUBQUMNDWOKJTVANCNFSM6AAAAAATAF7GOU>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
@creek23 seems like expected and current behavior added is same , will you be able to help with little more details on what exactly the issues is, so that i can try to reproduce. |
@amitpersonal007 the word |
The issue has been resolved |
Is there an existing issue for this?
What is the current behavior?
getting this step: Store current Test... value into runtime varible attribute
What is the expected behavior?
should be: Store current Test... value into runtime variable attribute
Steps To Reproduce
Provided fix on my fork: https://github.com/creek23/testsigma
Version
Testsigma Community Edition
The text was updated successfully, but these errors were encountered: