add typing to tests/test_protocol*

[dimastbk]

Changes

Fixes #

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• Add a new news fragment into the CHANGES folder
  • name it <issue_id>.<type> (e.g. 588.bugfix)
  • if you don't have an issue_id change it to the pr id after creating the PR
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.00%. Comparing base (c759664) to head (390072f).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1005      +/-   ##
==========================================
- Coverage   95.04%   95.00%   -0.04%     
==========================================
  Files         114      114              
  Lines       16917    16905      -12     
  Branches     2757     2758       +1     
==========================================
- Hits        16079    16061      -18     
- Misses        493      497       +4     
- Partials      345      347       +2     

Flag	Coverage Δ
cext	91.90% <100.00%> (-0.06%)	⬇️
integration	94.65% <100.00%> (-0.04%)	⬇️
purepy	94.46% <100.00%> (-0.06%)	⬇️
unit	52.73% <100.00%> (-0.05%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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