Look into re-enabling 11t tests

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Domain
testing-qa

Research direction

Start by reading the linked OpenVPN issue 1058 and the current 11t test setup. Compare the master path after the session management cleanup in the multipeer branch with the option of targeted fixes for 2.7. Done when the re-enablement scope is decided and the relevant tests run successfully.

Written by the indexing model from the issue text.

Description

See https://github.com/OpenVPN/openvpn/issues/1058

Need to decide whether to only re-enable for master after the session management cleanup in multipeer branch or to merge targeted bugfixes into 2.7 as well.

Dominant language
HCL
Stars
0
Forks
5
Avg merge
6d 21h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenVPN/openvpn-tests

All issues in OpenVPN/openvpn-tests

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.