Re #616 - content trigger - adding extra test (#620)

This commit is contained in:
dgtlmoon
2022-05-25 15:03:23 +02:00
parent f47c2fb7f6
commit 341ae24b73
2 changed files with 14 additions and 5 deletions

View File

@@ -293,10 +293,13 @@ class base_html_playwright(Fetcher):
# Better to not use any smarts from Playwright and just wait an arbitrary number of seconds
# This seemed to solve nearly all 'TimeoutErrors'
extra_wait = int(os.getenv("WEBDRIVER_DELAY_BEFORE_CONTENT_READY", 5)) + self.render_extract_delay
p=time.time()
page.wait_for_timeout(extra_wait * 1000)
except playwright._impl._api_types.TimeoutError as e:
raise EmptyReply(url=url, status_code=None)
r=time.time()-p
x=1
if response is None:
raise EmptyReply(url=url, status_code=None)

View File

@@ -43,7 +43,7 @@ def set_modified_with_trigger_text_response():
Some NEW nice initial text</br>
<p>Which is across multiple lines</p>
</br>
foobar123
Add to cart
<br/>
So let's see what happens. </br>
</body>
@@ -60,7 +60,7 @@ def test_trigger_functionality(client, live_server):
live_server_setup(live_server)
sleep_time_for_fetch_thread = 3
trigger_text = "foobar123"
trigger_text = "Add to cart"
set_original_ignore_response()
# Give the endpoint time to spin up
@@ -133,10 +133,16 @@ def test_trigger_functionality(client, live_server):
# https://github.com/dgtlmoon/changedetection.io/issues/616
# Apparently the actual snapshot that contains the trigger never shows
res = client.get(url_for("diff_history_page", uuid="first"))
assert b'foobar123' in res.data
assert b'Add to cart' in res.data
# https://github.com/dgtlmoon/changedetection.io/issues/616
# Apparently the actual snapshot that contains the trigger never shows
res = client.get(url_for("diff_history_page", uuid="first"))
assert b'Add to cart' in res.data
# Check the preview/highlighter, we should be able to see what we triggered on, but it should be highlighted
res = client.get(url_for("preview_page", uuid="first"))
# We should be able to see what we ignored
assert b'<div class="triggered">foobar' in res.data
# We should be able to see what we triggered on
assert b'<div class="triggered">Add to cart' in res.data