►
From YouTube: The Maintainers: Brad Wilson and xUnit
Description
Who is Brad Wilson?
I'm a software developer by trade, which I've been doing full time since 1993. I've lived and worked in many places in the United States, including Michigan (where I grew up), Massachusetts, Colorado, and Washington State where I reside now. I've visited all 50 states, and a dozen countries.
I've worked on some things you may have heard of, like ASP.NET MVC, Enterprise Library, and CodePlex. I've done startups and big companies, and tend to like smaller teams. I currently work at GitHub on internal developer tooling. I've also been involved in open source; I am the primary maintainer of xUnit.net, a unit testing framework for .NET developers (since 2007). I live stream on Twitch usually once a week, working on the next version of xUnit.net.
In my personal life, I am someone who consumes and occasionally produces music (mostly guitar, piano, and singing). I love playing games, especially board games, card games, and video games. I spend my outdoor time split between being on the water in a kayak or a raft, and on the road on my motorcycle.
- Brad Wilson's Blog: https://bradwilson.io/
- xUnit: https://github.com/xunit/xunit
A
A
A
I
feel
like
working
on
open
source
has
helped
me
in
the
sense
that
it
opens
opportunities
for
me
when
people
find
out
that
I
work
on
open
source
when
they
find
out
what
project
I've
worked
on,
and
so
I've
got
to
meet
a
lot
of
people.
I've
gotten
to
go.
Give
talks
about
x
unit
that
you
know
those
are
things
I
probably
wouldn't
have
been
able
to
do.
Had
I
not
been
working
on
the
next
unit,
and
in
fact
you
know,
I
would
say
that
I
was
more.
A
You
know
getting
out
and
getting
on
the
speaking
circuit
was
something
happened
earlier
for
actually
done
that
than
later
for
me
with
asp.net.
So
by
the
time
you
know,
I
started
doing
talks
for
asp.net
as
well.
You
know
I
already
had
that
experience,
which
is
also
very
nice,
that
it
helped
me
sort
of
get
a
jump
start
on
that,
but
it
certainly
opens
doors.
I
don't
think
it
necessarily
does
that
for
everybody,
but
I
do
believe
that
you
know
it.
A
It
can
be
helpful
if,
for
your
career,
for
people
to
be
able
to
look
at
a
body
of
work,
that
really
is
something
that
was
driven
just
by
you
or
just
by
you
and
a
couple
of
friends
to
be
able
to
say
you
know
this
was
not
driven
by
any
corporate
decisions.
This
was
not
driven
by
anything
like
that.
It
was
really
just
us
thinking
about
what
do
we
want
and
interacting
with
the
community.
A
A
Is
you
know
an
attempt
to
do
that.
My
big
project,
which
you
know
most
people
probably
know
me
for
xunit.net,
started
out
as
an
internal
tool
and
we
really
sort
of
lobbied
to
make
that
be
available
to
everybody
everywhere,
so
they
could
use
it
as
well.
So
that's
always
been
my
my
primary
driver
for
doing
open
source.
A
I
spend
probably
one
day
a
week
working
on
my
open
source
projects
on
average.
Sometimes
it's
a
little
bit
more
like
right.
Now,
I'm
trying
to
get
version
three
out,
and
so
I'm
working
mostly
on
saturdays
and
sundays.
Right
now
there
will
be
times
when
I
don't
work
at
all
on
it
during
the
week,
and
so
I
only
work
on
it
in
my
personal
time.
My
my
day
job
is,
you
know
my
day
job
hours,
so
I
only
work
on
the
weekends.
A
The
contribution
model
for
x
unit
really
sort
of
falls
into
two
camps,
one
obviously
jim
newkirk
and
I
were
the
original
founders
of
the
project.
So
we
have
a
lot
of
our
of
our
own
code
in
there.
The
vast
majority
of
it
is
just
code
from
us
and
when
we
first
went
open
source
from
microsoft,
we
was
really
more
of
a
shared
source
model.
A
It
wasn't
really
an
open
source
model
once
the
project
got
out
of
microsoft's
ownership
into
what
was
at
the
time,
the
codeplex
foundation,
which
became
the
outer
curve
foundation,
and
then,
when
that
disappeared,
went
to
the
net
foundation,
basically
once
it
once
it
left.
Microsoft,
we
started
taking,
you
know,
actual
code
contributions
and
so
there's
really
sort
of
the
core
team.
Jim
isn't
involved
so
much
anymore.
So
mostly
it's
me
and
claire
novotny.
A
She
owns
the
visual
studio,
runner
and
the
devices
runner,
and
I
own
pretty
much
everything
else
and
then
from
the
outside
community.
Most
of
the
time
I
would
say
the
majority
of
the
contributions
we
get
are
bug
reports
and
feature
requests
through
the
issue
tracker,
and
then
we
do
get
prs.
I'd
say
that
those
pr's
come
from
a
mix
of
places,
there's
a
significant
amount
of
contribution
from
a
third-party
perspective,
from
teams
at
microsoft,
because
there
are
a
lot
of
teams
at
microsoft
to
use
x
unit.
A
So
the
rosalind
team.net
team
are
a
couple
of
big
contributors,
and
then
you
know
just
the
general
public:
they
they
see
a
feature
they
want,
or
they
see
one
of
our
up
for
grabs
issues
on
our
repository
and
they
just
grab
it
and
do
the
pr
so
from
a
core
committer
perspective.
You
know:
we've
really
probably
only
had
four
or
five
people
over
over
the
years
in
that
model.
A
So
the
what
became
the
analyzers
for
actually
done,
that
he's
no
longer
maintaining
that,
but
he
did
a
tremendous
job
sort
of
getting
it
off
on
its
feet,
and
so
I
sort
of
brought
that
back
in.
We
don't
really
solicit
for
core
contributors
much
it's
just
you
know.
People
who
have
made
lots
of
contributions
will
generally
sort
of
just
take
their
contributions
without
too
much
fuss,
but
like
people
who
have
you
know
just
direct
right
access
to
the
to
the
repos.
At
this
point,
that's
just
that's.
Basically,
just
me
jim
and.
A
Claire
version
one
lasted
for
about
five
or
six
years,
I
would
say
we
iterated
on
version
one
basically
just
doing
on
diversion
updates
at
that
time
and
for
version
two.
We
didn't
really
follow
the
semantic
versioning
model.
From
our
perspective,
you
know
we
looked
at
major
versions
as
major
feature
additions
and
major
architectural
overhauls.
So
in
v2
we
wanted
to
do
cross-platform
support,
so
that
meant
both
adding
support
for
other
windows-like
platforms.
A
So
at
the
time
that
was
silverlight,
and
then
it
became
windows,
phone
and
uwp,
but
also
being
able
to
support
running
tests
on
mono
both
on
linux
macos,
but
also
on
ios
and
android
through
mana
and
then
version
three
has
really
been
yet
another
architectural
sort
of
overhaul.
That
was
inspired
by
some
limitations
in
our
design
that
we
discovered
with
net
core
and
so
just
wanting
to
go
back
and
and
and
make
some
big
fundamental
changes
to
some
of
those
decisions
we
made
and
again
that
lasted
about
five
or
six
years.
A
We
just
sort
of
take
the
feature,
requests
and
the
bug
requests
as
they
come
in.
We
collect
them
to
the
point
where
we
think
you
know
hey
this.
This
amounts
to
enough
to
make
a
release
and
then
release
them
so
that
that
part
of
it
also
feels
a
little
bit
ad
hoc,
but
I
think
it's
reactive
to
what
the
community
is
looking
for
from
us.
A
The
support
we
get
from
the
foundations
has
primarily
been
what
I
would
call
legal
support,
and
that
means
a
couple
of
things
for
us
one
is:
the
foundation,
helps
us
from
a
legal
liability
perspective
in
the
sense
that
they
own
the
code,
and
if
someone
were
to
come
and
challenge
the
ownership
of
the
code,
it
would
be.
You
know
us
and
then
together
defending
the
code,
but
it
also
helps
us
from
a
legal
perspective
of
contributions.
A
Before
we
had
the
foundation,
you
know
when
things
were
in
microsoft.
We
really
couldn't
take
contributions,
because
microsoft
wasn't
really
set
up
at
that
point,
to
be
able
to
accept
contributions
to
microsoft,
owned
code,
and
so
the
foundation
gave
us
the
ability
to
set
up
a
framework
of
contribution
license
agreements
for
code,
that's
contributed
and
what's
really
nice
about
the.net
foundation.
Version
of
that
is.
A
Unlike
when
we
were
in
the
codeplex
outer
career
foundation,
everybody
had
to
sign
their
own
legal
agreement
for
each
project
that
was
there
in
a.net
foundation.
Once
you've
signed
a
contribution
agreement
with
the
net
foundation,
it
applies
to
all
the
projects
in
a.net
foundation.
That's
also
very
nice.
So
we
have
a
thousands,
I'm
sure
of
people
who've
already
signed,
that
agreement,
who
are
basically
legally
ready
and
capable
of
making
contributions
and
that
that's
a
huge
win
for
us.
So
the
source
code
started
out
on
codeplex.
I
worked
on
codeplex.
A
I
was
there
for
the
launch
jim
newkirk,
who
was
the
other
founder
of
xun.net.
He
also
worked
on
n
unit,
so
unit
testing
was
clearly
something
that's
sort
of
in
his
dna.
We
were
both
on
codeplex
at
the
time.
Jim
ran
the
team,
and
I
was
one
of
the
developers,
and
so
we
used
it
at
codeplex
before
complex,
so
the
source
was
on
codeplex,
even
when
it
was
a
private
project.
Once
it
went
public.