Page 1 of 1

Overview of test

Posted: 2018-Aug-04 8:16
by 3DfromNULL
I don't open the source code of the plugin to the public at this point in time. The specification document is the tSxAPIxx.doc and a tester need to make sure that test scripts can call each tsxAPI function and can get right results from it. The results to be checked include returned values, changed parameters (elements in list objects), changing of trueSpace (tS) scene, changing of tS parameters, etc. The number of the tsxAPI function is differ (600 thru 1200) by tS version, and C/C++ callback functions are registered in some cases.

You may want to exhibit some test scripts without preamble. But how can we avoid duplicated tasks? If some coordinators or moderators are necessary, how should we decide them?