You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*Unit Tests break when specific string is entered in .lslt (both test run and test editor fail) https://code.google.com/archive/p/lslforge/issues/6
Posted on Nov 23, 2011 by Happy Horse
What steps will reproduce the problem? 1. With a function similar to this one: string InterpretSpecialCommands(string specialcommand,string Username,key Userkey) 2. Create a test that tries to call the function with specialcommand as in the following line: Shout:8,au4gp734ga34GQ§H$§$a48gö847agfugfgaweugiöeurigfiuerhlösehrgheriusleughlsehrkgjshgjhskdfgkjesrhgkjserhlgkjserhgkjsehkjrghlkejrhkejhlksgj 3. Try to run the test -> test does not even start 4. Close the test file and try to open it again -> exception
What is the expected output? What do you see instead? Running the tests
What version of the product are you using? On what operating system? LSLForge 0.1.0 win32
The text was updated successfully, but these errors were encountered:
*Unit Tests break when specific string is entered in .lslt (both test run and test editor fail)
https://code.google.com/archive/p/lslforge/issues/6
Posted on Nov 23, 2011 by Happy Horse
What steps will reproduce the problem? 1. With a function similar to this one: string InterpretSpecialCommands(string specialcommand,string Username,key Userkey) 2. Create a test that tries to call the function with specialcommand as in the following line: Shout:8,au4gp734ga34GQ§H$§$a48gö847agfugfgaweugiöeurigfiuerhlösehrgheriusleughlsehrkgjshgjhskdfgkjesrhgkjserhlgkjserhgkjsehkjrghlkejrhkejhlksgj 3. Try to run the test -> test does not even start 4. Close the test file and try to open it again -> exception
What is the expected output? What do you see instead? Running the tests
What version of the product are you using? On what operating system? LSLForge 0.1.0 win32
The text was updated successfully, but these errors were encountered: