Running system under test from tlsfuzzer

Open
#46 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Start with tests/scripts_retention.py, which the issue identifies as the existing SUT runner, and review the dependency in issue #58. The work is done when tlsfuzzer can select or generate key files, restart the server after crashes, and support running the SUT under valgrind or collecting core files.

Written by the indexing model from the issue text.

Description

complex enhancement

Allow the tlsfuzzer to run the SUT by itself, needed to run the SUT with valgrind or to collect core files.

While the tests/scripts_retention.py essentially can do that, it's quite stupid about it – can't select key files (or generate them itself on demand), restart the server when it crashes, etc.

depends on #58

Dominant language
Python
Stars
635
Forks
140
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 tlsfuzzer/tlsfuzzer

All issues in tlsfuzzer/tlsfuzzer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.