DynamoRIO/drmemory

Set up Wine and Reactos tests under Dr. Memory

Open

#338 opened on Nov 28, 2014

View on GitHub
 (6 comments) (0 reactions) (0 assignees)C (289 forks)auto 404
Component-TestsMigratedOpSys-WindowsPriority-Mediumhelp wanted

Repository metrics

Stars
 (2,727 stars)
PR merge metrics
 (PR metrics pending)

Description

From timurrrr@google.com on March 16, 2011 11:05:58

An idea came to me how we can improve the test coverage for Dr. Memory and DR - we can use existing Wine tests!

There are ~170 test cases, downloadable from (a link at the bottom of the page) http://test.winehq.org/ I'll try setting up these test on our buildbot to test Dr. Memory

Original issue: http://code.google.com/p/drmemory/issues/detail?id=338

Contributor guide

Research direction
Study the Wine test infrastructure (wine test suite, test scripts, and how tests are run). Understand Dr. Memory's build system and how it integrates with other testing frameworks. Look at existing Dr. Memory tests for patterns. Then design a way to run Wine tests under Dr. Memory, likely by wrapping the test executables with Dr. Memory's tool.
Tech stack
c
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CTesting frameworksWine internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40