No, I don't think you cover my workload. That's why I asked
However, since I've thought up how to implement most of that, I'll get something together.
Fair enough.
What to simulate:
A: Browser with 2 dozen tabs open. Compulsively refreshed between matches.
B: The game being played.
C: Blu-Ray transcoding.
D: Hulu, Netflix, or previously ripped movie playing on second screen.
E: BOINC or FAH making use of leftover resources.
A
CMARK, memory reviews, usage testing. I do have a personal set of tests I do, and I do use each board for most of the week. I do collect numbers that I do not report as boards tend to make little difference that can be numerically valued.
B:Game tests. I report with apps that react to motherboard differences.
C:Handbrake(I encode custom-made AVI to H.264, takes 5 minutes per run, I do 5 runs each test)
D:not covered, but I do exactly this testing while gaming. I usually sit in the BF3 TS when doing this testing, so many members do even hear of issues as they happen. If there is something that sticks out, It's mentioned in the review, but since that is more a VGA test than a motherboard test, and I am not reviewing videocards, it doesn't take a priority among things I report on. I use second screen for TS, AIDA64 for monitoring, and usually some sort of video from links dropped by TS members. It's testing, in a way, but really, that's just how I use my PC, as do most people!
E:Although not exactly in graph form, power consumption testing is done exactly so, but using Prime95 as the app to load the rest of the chip. Actually reporting this as a numerical value is kind of hard, but that testing does get done.
Really the issue comes down to being able to put this sort of feedback into a graph.