Automated Test Excution not shown on Squash TM

[chatim]

Hi @yamina,
Thank you very much for the infos.
have a great day

[narsuman]

Hello from Finland!

I am sorry about my English, but I hope you can translate this quite easily.

At first I would like to thank you for interesting tool project I have been evaluating Squash stack to be used as a tool for software testing training.
I have been using Testlink and some other tools quite many years and I have been searching for suitable replacement. I hope I have found it now
You have done great job!

BACKGROUNDING:

I have been trying to setup Squash TM + OTF + RF + Presta Shop as SUT.
Setup is almost working, but I noticed same kind of problems (earlier in this thread) with my current setup:

PROBLEM:

There is no any progress reported at execution window? Only job id visible on screen. I still can see test progressing at orchestrator(workflow exists) and RF case is executed with PASS, but the results are no reported to Squash TM?

CURRENT CONFIGURATION:

- Squash TM server has own public IP (HTTPS with proxy)
- Orchestrator has own public IP (HTTP + TOKEN)
- SUT has own public IP

POSSIBLE REASONS:

I have created self signed SSL certificate for my Squash TM server and I have Apache proxy to server HTTPS. My question is Do I have to make orchestrator some how trust for my self signed certificate at Squash server side?

BR,
Marko "NarsuMan" Rintamäki

[narsuman]

I have done some steps after my last message:

-I have added "server.crt" file at orchestrator vm so now I can access my Squash TM server without problem. There is no messages like "not secure certificate" etc
-Upgraded Result Publisher 6.0.0 -> 6.0.1


I assume Squash TM server is fetching execution status from Orchestrator's Port 38368? It's visible to outside world??

But still no results?

No progress.png (29.92 Kio) Consulté 284 fois

Br,
NarsuMan

[kasia_klepacka]

Hi Marko,

It seems like Squash TM can reach the Orchestrator, but the communication is obstructed the other way round. For guidance on declaring a self-signed certificate for the Orchestrator, you can check out this link: https://autom-devops-en.doc.squashtest. ... certs.html.

If you're still facing issues after following the information provided, I have a few questions for you. Please bear with me if any of these seem repetitive, I apologize in advance:

1) Could you attempt to send a curl request from the OTF container using the following command? curl https://squashtm.example.com/squash/isSquashAlive
2) Which version of the Orchestrator (OTF) are you currently using? (I'm assuming that you are using Squash TM 6.0.1, considering the plugin upgrade you mentioned).
3) Would it be possible for you to share any logs from Squash TM and the Orchestrator that are related to the execution?

Was this information of any help to you?

Best regards,
Kasia

[narsuman]

Thank you for support! I hope we can debug this problem together

1. Here are some results from Curl

root@ae482444c998:/app# curl https://vm1234.xyz.fi/squash/isSquashAlive
Squash is Alive!root@ae482444c998:/app#

2, OTF is using latest Docker image: opentestfactory/allinone:latest

sudo docker run -d --name orchestrator --link=robotenv -p 7774:7774 -p 7775:7775 -p 7776:7776 -p 38368:38368 -e SSH_CHANNEL_HOST=robotenv -e SSH_CHANNEL_USER=otf -e SSH_CHANNEL_PASSWORD=siicret -e SSH_CHANNEL_TAGS=ssh,linux,robotframework -e SSH_CHANNEL_PORT=22 -e DEBUG_LEVEL=DEBUG -v /etc/ssl/certs/:/etc/ssl/certs/ -v /home/ubuntu/data/trusted_key.pub:/etc/squashtf/trusted_key.pub opentestfactory/allinone:latest

3. There is no currently proxy/https used at Orchestrator VM

4. Execution log at orchestrator side: Here is also log from Orchestrator Container as attachment

Test case activation is found from log at line 520 ">>>>>>>TEST CASE EXECUTION>>>>>>"

orchestrator-log.txt

(710.29 Kio) Téléchargé 6 fois

[narsuman]

I am trying next update Squash TM 6.0.0 -> 6.0.1

Same results with Squash TM 6.0.1

br,
NarsuMan

[kasia_klepacka]

Hello,

Ok, it seems like the Orchestrator can contact Squash TM correctly.
Can you tell me if you have the correct plugins for the 6.0.1 version (you can check them at <your_squash_url>/administration-workspace/system/information?anchor=information:

• automation.result.publisher-6.0.1.RELEASE.jar

• automation.scm.git-6.0.0.RELEASE.jar

• automation.squashautom.community-6.0.0.RELEASE.jar

• automation.testplan.retriever.community-6.0.0.RELEASE.jar

Can you also send me the logs from Squash TM and the result of the command opentf-ctl version from the inside of your otf container?

UPDATE: Could you add the following environment variable to your deployment command:
-e CURL_CA_BUNDLE=/etc/ssl/certs/<your certificate name>


Best regards,
Kasia

[narsuman]

Hi!


Just a check: DO I need to set certificate if I am trying first setup orchestrator with http+token connections? I could add more security later when basic functionality is working first ?

Here below is log attached from Squash TM 6.0.1

IP's changed

Orchestrator at 196.168.31.89

Installed plugins

api.rest.core-6.0.0.RELEASE.jar
api.rest.services-6.0.0.RELEASE.jar
automation.result.publisher-6.0.1.RELEASE.jar
automation.scm.git-6.0.0.RELEASE.jar
automation.squashautom.community-6.0.0.RELEASE.jar
automation.testplan.retriever.community-6.0.0.RELEASE.jar
bugtracker.gitlab-6.0.0.RELEASE.jar
org.eclipse.jgit-6.4.0.202211300538-r.jar
report.books.requirements.editable-6.0.0.RELEASE.jar
report.books.requirements.pdf-6.0.0.RELEASE.jar
report.books.testcases.editable-6.0.0.RELEASE.jar
report.books.testcases.pdf-6.0.0.RELEASE.jar
sync.xsquash4gitlab-6.0.0.RELEASE.jar

opentf-ctl version

Tools Version: version.Info{Major:"0", Minor: "45", FullVersion: "0.45.0"}
Orchestrator:
Orchestrator server: http://localhost
Components of otf-images image:
allure: 2.13.8
opentf-orchestrator: 0.61.0
opentf-qualitygate: 0.16.0
org.opentestfactory:micronaut-java-plugins: 1.6.0


br,
NarsuMan

[narsuman]

Last message still waiting moderation??

[narsuman]

Now certificate issue fixed. No progress...

About my setup: (ip changed)

Squash TM VM in own public ip: 123.123.123.123
Orchestrator VM in own public ip: 125.12.23.23 running as container (172.17.0.3)
Robot Framework runner in docker inside Orchestrator

I did some debug with container lever.. I am little bit lost? Is there problem with orchestrator who cannot find Squash TM??
So I assume there is some problem with DSN in container level?

I added message sequence diagram about steps during test automation execution

pcap-and-sequence during test-execution.pdf

(3.28 Mio) Téléchargé 7 fois

.. and some frames

dns querys.png (53.94 Kio) Consulté 196 fois

I have also executed Now open-otf client from other virtual machine and it seems workflow is executed correctly:

WORKFLOW_ID STATUS NAME
f74d45fa-5d96-456c-bae1-e5df010a299e DONE Workflow for Squash TM test suite: Tukko V1.1 > CAMP1 > ITE1 > Automation 1
ubuntu@squash-tm-2:/home$ opentf-ctl get workflow f74d45fa-5d96-456c-bae1-e5df010a299e
Workflow Workflow for Squash TM test suite: Tukko V1.1 > CAMP1 > ITE1 > Automation 1
(running in namespace 'default')
[2024-03-11T08:52:23] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Requesting execution environment providing ['robotframework'] in namespace 'default' for job 'squashTMJob-0'
[2024-03-11T08:52:23] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Running function actionscheckoutv2
[2024-03-11T08:52:24] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Cloning into 'presta-shop-tests'...
[2024-03-11T08:52:24] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] warning: redirecting to https://gitlab.branet.jk.fi/shared/pres ... tests.git/
[2024-03-11T08:52:24] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Running function robotframeworkparamsv1
[2024-03-11T08:52:25] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Running function robotframeworkexecutev1
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] ==============================================================================
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] 244 Standard account creation :: Fixing not running test case
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] ==============================================================================
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Standard account creation
| PASS |
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] ------------------------------------------------------------------------------
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] 244 Standard account creation :: Fixing not running test case | PASS |
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] 1 test, 1 passed, 0 failed
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] ==============================================================================
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Output: /home/otf/d89e80ee-fda9-43be-9253-3a6ab43edd50/output.xml
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Log: /home/otf/d89e80ee-fda9-43be-9253-3a6ab43edd50/log.html
[2024-03-11T08:52:47] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Report: /home/otf/d89e80ee-fda9-43be-9253-3a6ab43edd50/report.html
[2024-03-11T08:52:50] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] find: 'browser/screenshot': No such file or directory
[2024-03-11T08:52:51] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] find: 'browser/screenshot': No such file or directory
[2024-03-11T08:52:51] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] find: 'browser/screenshot': No such file or directory
[2024-03-11T08:53:00] [job d89e80ee-fda9-43be-9253-3a6ab43edd50] Releasing execution environment for job 'squashTMJob-0'
Workflow completed successfully.

It seems that problem is at Squash TM side? Why progress bar is not actively updating? If Workflow is accessible by client (at other vm) there should be no problem at orchestrator side? I cannot see any error messages about connection timeout etc...






BR,
NarsuMan