Output attempted address in strict mode

[wilhelmklopp]

This is another change on the back of #295 – I made this locally and it helped quite a bit as i was migrating from httpretty to mocket. This way you can see which url the test tried to access, but couldn't.

Was specifically quite helpful in figuring out the querystring issue. Example output:

mocket.exceptions.StrictMocketException: Mocket tried to use the real `socket` module while STRICT mode was active.
Attempted address: slack.com:443
First request line: GET /api/users.list?team_id=T_e2e_correctly_calculates_enterprise1&limit=500 HTTP/1.1
Registered entries:
  ('slack.com', 443):
    Entry(method='GET', schema='https', location=('slack.com', 443), path='/api/users.list', query='')

Feel free to edit the code or make a separate PR if there's a better way to do this. I think the code works fine as-is for http mocking, but haven't tested with any kind of other socket.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.72%. Comparing base (713ccd6) to head (8b3a706).
Report is 1 commits behind head on better-strict-mode.

Additional details and impacted files

@@                  Coverage Diff                   @@
##           better-strict-mode     #296      +/-   ##
======================================================
+ Coverage               98.71%   98.72%   +0.01%     
======================================================
  Files                      22       22              
  Lines                    1010     1019       +9     
======================================================
+ Hits                      997     1006       +9     
  Misses                     13       13              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mindflayer]

What if we allow redefining the MocketMode class instead? So you could pass a class that implements what you need. Of course, we would keep the change that makes Mocket sending more information to the function when raising the error.

[wilhelmklopp]

ah interesting so like another mode besides strict_mode=True ? i think that would work for me 👍

[mindflayer]

I changed my mind, kept your code and just changed First request line to a more protocol-agnostic Sent data. Hope you won't mind the change.

[mindflayer]

@wilhelmklopp Here is the release with a better strict mode:
https://pypi.org/project/mocket/3.13.9/

[wilhelmklopp]

@mindflayer very exciting, thanks! 🎉