DavidE
Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Script Extension Help
Robert, I have started trying to add the various parts of the actual routines since apparently the stub records don't work. I am now returning the boolean as you suggested and referenced in the document, but TestComplete is still crashing. I have attached my updated files. I still haven't added the code that would run on execution, but that should not be relevant to testing if this will import.Re: Script Extension Help
Thank you for the reply. Currently, there is non functionality of my script extension, because when I try to enable anything TestComplete just crashes on me. Again, I am sure I am doing something wrong, but can't seem to determine exactly what. Let me describe what we are wanting to do as their may be a better way to do this than the path I am trying to go down. Goal: Produce a text based log file which we can upload as an artifact into our change system that indicates that the test ran successfully. Our change system will not allow large files or MHT extensions to be uploaded into it. I wrote a function that writes out to a text log file that we can upload as an artifact. It functions much like the existing Log.Message function, but instead of writing into the TestComplete log, it just writes into a standard text file. We are then putting this logging function before and after a checkpoint. Indicating that we are attempting to validate the object/property. And then afterwards that we successfully validated the object/property. Because the test fails on error, what we see in the log is that we are attempting to validate, but never get a success message. This is OK, but obviously could be better. So it takes 3 steps to preform this, and the wording that each team member puts into the messages is inconsistent, therefore the output from test to test is not the same. My hope was to write a script extension that did this all in one step and the messages we write to the log file could be embedded into the extension so that they are consistent. Seemed simple enough, but I can't seem to figure out what it is I am doing wrong that is causing the script extension to crash. I even stripped it down to a very basics setup that didn't really do anything thinking a clean slate would get me started. I assume it has something to do with the relationship between the description.xml and the script file that I am just not getting.
