Does TestComplete 8 have card reading capabilities?

Hi Molly,



Generally speaking, you should be able to do what you need.

To get more exact piece of advice more details are needed because the "Member not found" error says practically nothing (it is even not clear if the error is from TestComplete or from the tested application/smart card software).

The actual approach depends on how the smart card software works and how the web site interacts with it.

Once upon a time I automated something like that (it was done with TestComplete 3), but in my case the smart card software had a user interface where it was possible to enter PIN and that popped-up if connection was broken. So there was nothing special in my case: script established connection via smart card (obviously, smart card had to be in the reader) and than performed required actions. If some action failed to execute, the script verified if it was because of disconnection (and tried to reconnect then) or because of some other problem.

If your smart card software does not have user interface, then you should consult with developers and ask them how to login via API.

Okay, I am also getting this error a lot, but I'm not sure what it means, I am not stopping the test manually:



Possible reasons:
- An error or warning occurred during the test run. See the preceding log entries to locate and identify the error.
- The test run was stopped manually.
- The test run was terminated as a result of the Runner.Halt method call.Possible reasons:

- An error or warning occurred during the test run. See
the preceding log entries to locate and identify the error.

- The test run
was stopped manually.

- The test run was terminated as a result of the
Runner.Halt method call.

Hi Molly,



Actually, the message means exactly what it says: the test was terminated before it reached its end. There may be different reasons of why the test was terminated and the message mentions major of them. If you did not stop test manually, then you should look into the log for other error messages, analyze them and decide what action could terminate the test.