Several observations while using Tera Term for routine task automation
- Since the task supposed to take quite some time, my intention was to start it and continue working on something else. Unfortunately I was not able to accomplish this because every time SSH Authentication window popups up, it steals the focus from active application, i.e. I was not able to write emails and do other work. Neither setting showtt 0, nor minimizing Tera Term window changes this annoying behavior.
- If SSH login fails due to incorrect credentials testlink command is not able to identify it. The macro goes into waiting loop and there is no indication of what happened. Only after terminating the macro and closing Tera Term main window the error message appears saying that user credentials were invalid. I expect the same will happen if authentication method (password, challenge, etc) is incorrect, but I have not tested that. There should be a better way to handle such scenarios.
- After failure to log in as described in the previous item I tried to pause and resume macro. This unexpectedly caused new Tera Term window to open and macro script continued running there. I was logging the session and to continue logging under this behavior I had to move logopen and logclose commands inside the loop.
- /nosecurity argument of connect command (which is by the way not documented in Help) suppresses the warning popup, however it does not add the signature to ssh_known_hosts file. Not sure if this is a bug or as per design. In either case this is not the behavior user may expect.
- There was number of times when the 1st sendln command after establishing the connection would not appear on the screen and in the log file, nevertheless it was preceded by wait for prompt command. Considering that I was not able to do anything else due to the 1st issue in this list and that I used setsync command in my macro, it would be interesting to know if I reached the capacity limits of the application.