screenshot step cannot cap image

[andychan06]

问题描述 / Describe the bug
screenshot step succeed, but no image can be found. Also the time of screenshot in report shows 00:00:00.000

问题复现步骤 / To Reproduce

1. use Background with more than 2 steps
2. screenshot in Scenario
3. find screenshot

预期结果 / Expected behavior
image should be found

截图 / Screenshots

环境信息 / Environment (please complete the following information):

• Device: [Pixel 4A]
• OS: [Android 12]

Additional context

[andychan06]

seems like /default/screen.py:

if len(scenario.steps) > step_index >= 0:

this guard makes screenshot not run?

[xiaoxiaocaiiao]

cannot repro please share the run log. By the way do you find the msg "[screen_link_to_behave]" in the run log?

[andychan06]

[screen_link_to_behave]

cannot find this message.

my test example from ctrip:

  # language: en
 Feature: flybirds test feature-android click

  Background: 
      When start app[ctrip.android.view]
      And page rendering complete appears element[text=机票]

   Scenario: test click--click position
     And  click position[580,1200]
     And  wait[5]seconds
     Then screenshot
     Then close app

And the result

And the print log
log.txt

There is nothing captured in the screenshot folder.

[xiaoxiaocaiiao]

een..., it seems that only before step hook is run, but screen step logical is skiped, please debug as below pic:

run script please use( "./features/test/android/base_en_click.feature --format=json -o report/1ae9c606-8943-48ec-b0cb-b3e02239fb13/report.json --define screenShotDir=cmVwb3J0LzFhZTljNjA2LTg5NDMtNDhlYy1iMGNiLWIzZTAyMjM5ZmIxMy9zY3JlZW5zaG90 --define run_at=bG9jYWw= --no-color --no-capture --no-capture-stderr" ) and tell me what happen here.

[andychan06]

een..., it seems that only before step hook is run, but screen step logical is skiped, please debug as blow pic:

run script please use( "./features/test/android/base_en_click.feature --format=json -o report/1ae9c606-8943-48ec-b0cb-b3e02239fb13/report.json --define screenShotDir=cmVwb3J0LzFhZTljNjA2LTg5NDMtNDhlYy1iMGNiLWIzZTAyMjM5ZmIxMy9zY3JlZW5zaG90 --define run_at=bG9jYWw= --no-color --no-capture --no-capture-stderr" ) and tell me what heppen here.

The problem cannot be reproduced using the demo Ctrip project with my testing feature?

[xiaoxiaocaiiao]

yes, we are used same demo, i cannot repro on windows os. maybe only mac os has this issue, i will try latter. by the way please report the issue also atthed the machine os.

[andychan06]

yes, we are used same demo, i cannot repro on windows os. maybe only mac os has this issue, i will try latter. by the way please report the issue also atthed the machine os.

yes, I am using macOS. Btw sorry I may need more time to setup Python from your screenshot configs as I have no experience doing this.

[andychan06]

tried your suggestion.
reproduce.txt

Please have a look

[xiaoxiaocaiiao]

tried your suggestion. reproduce.txt

Please have a look
when you complete my suggestion, you can hold on the below code when debug the test case, and see what happen here.
seems like /default/screen.py:

if len(scenario.steps) > step_index >= 0:

this guard makes screenshot not run?

[andychan06]

yes, the if statement guards the screenshot

 # language: en
 Feature: flybirds test feature-android click

  Background: 
      When start app[ctrip.android.view]
      And page rendering complete appears element[text=机票]

   Scenario: test click--click position
     And  click position[580,1200]
     And  wait[5]seconds
     Then screenshot
     Then close app

[xiaoxiaocaiiao]

yes, the if statement guards the screenshot

 # language: en
 Feature: flybirds test feature-android click

  Background: 
      When start app[ctrip.android.view]
      And page rendering complete appears element[text=机票]

   Scenario: test click--click position
     And  click position[580,1200]
     And  wait[5]seconds
     Then screenshot
     Then close app

use the workaround : add background to scenario。 i will try to run it and find the final solution。

[andychan06]

Thanks @xiaoxiaocaiiao, I have used the workaround already.

Look forward to hearing any update.

[xiaoxiaocaiiao]

Thanks @xiaoxiaocaiiao, I have used the workaround already.

Look forward to hearing any update.
fix in latest build.

[andychan06]

Thanks @xiaoxiaocaiiao, I have used the workaround already.
Look forward to hearing any update.
fix in latest build.

@xiaoxiaocaiiao thanks for the update. Tested the latest build & confirm it is fixed.