Conversation
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
View the full list of 1 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
d944d8e to
149b4dd
Compare
|
Anyone had time to test this out yet? Just checking. |
|
Please let me know if there's anything faulty or missing from this PR and I will update. Thanks. |
|
Hi, thanks for the contribution! Could you add a test that asserts that it's working as expected? |
Test Steps
|
|
I'm looking for an automated test (pytest), thanks So basically add headers in the new/supported formats as a static file, while redacting confidential information No manual steps should be needed |
Done. |
|
Any feedback on my pytest? Thanks. |
|
Sorry I seem to have missed that. Thanks for adding the tests. At first glance it seems that a lot of tests are failing. Will have a look at the code later today. |
Ok, I better have another look at that too. I mistakenly thought it was the code coverage check failing to generate a report for some external reason, but upon closer look I see tests erroring out: |
…owser.json necessary for tests
|
Fixed issue with failing tests. It was because my new test was creating a new Now, there are two unrelated tests failing, both referenced in this other developer's PR from a couple days ago: #884 (comment) |
|
@sigma67 is the pipeline in a weird state currently with regard to secrets? I saw your comment on another PR and wondering if that's why the sudden errors with |
Fixes #857
Supports all three of the following formats for pasting headers:
Had to add a corner case to handled the odd
Decoded:header in Chrome, which looks like the following:It's the only one that still has a colon on the header key so it had to be handled differently. The end result in the parsed
user_headersis the same as it was before, where the property ends up beingDecoded: "}"