Off the bat with a subtle Nash equilibrium / Magic card reference. This can only be good, right?

// Here be Dragons

Of course we will.

Why?

Solid choice two years ago, but doesn't beat Mentors nor Eldrazis today.

It will get worse over time.

A Sorrow's Path, if you will.

Requirements

A condition or capability needed by a user to solve a problem or achieve an objective. A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document. A documented representation of a condition or capability as in 1 or 2.

Functional requirements!

It’s funny because this is kind of like a car and the banding ability is like collaboration.

Given a constructed Magic deck,

When I count the number of cards in the main deck

Then that number must be at least 60





Story: 93/94 Sligh deck

As an Old School Mtg player who enjoys trying different strategies

I want to build a monored Sligh deck

So that I can play it with friends and lend it out during tournaments





Scenario 1: We want to be able to lend the Sligh deck to other players in tournaments if we don't play it ourselves. As such, we want to have zero overlap between this deck and the Project M and Monogreen decks.

Given one player is playing the Project M deck

And one player is playing the Monogreen deck

When one player is playing the Sligh deck

Then all decks should be fully constructed without proxies





Scenario 2: We have access to a decent card pool, and should be able to build a solid Sligh deck without spending too much additional money on the project.

Given we need to buy cards to finish the Sligh deck

When we calculate the total cost for acquiring the cards

Then that sum cannot be higher than $100

Nothing like a picture of a wall of text to alleviate the monotony of a wall of text. Did some syntax highlighting though.

If you like testing non-functional requirements, some stuff Netflix do is basically nerd porn.

This is deploying it to a larger market without load testing it. Obama doesn't approve.

Off to development

TestIs9394MagicCard()

{

foreach (card c in slighdeck)

{

Assert(contains(c, 9394LegalCards))

}

}





TestNumberOfCardsInDeck()

{

Assert(slighdeck.decksize() >= 60)

}

Guess bugs are like Power in that aspect.

TestNumberOfOneDropPermanents()

{

Assert( (slighdeck.NumOfPermanentsWithManaCost(1) >= 8) && (slighdeck.NumOfPermanentsWithManacost(1) <= 13) )

}

Make it green!

Top-Down . What is there?

. What is there? Bottom-Up . What is not there?

. What is not there? Backwards . How did we get to the winning position?

. How did we get to the winning position? Forward. What’s the gameplan from turn one and forward?

The powercreep these days...

Might be that Dragon Whelp is a better 4-drop anyway...

This might work.

Forethought is 19/20.

63-card deck list on an airplane sick bag.

Feedback can be painful. Data help us avoid bias.

Project M v1.0, January 2013.

Test and release

The MVP for the Sligh deck.

Those lands can't be right...

This online deck builder is basically a continuous integration tool. It checks that I have the right amount of cards, that the deck is legal in the format, and can show me the mana curve as well as helping me draw sample hands.

Is this our data base?

Is it scary to make changes to your deck? Are you afraid it won't work? Do you want to spend days testing it manually before trying it out in a tournament? (Lacking automated test coverage)

If you rebuild the deck and it doesn't work that well anymore, can you quickly return it to the previous build that worked? Have you thrown away your old deck list or traded away the cards? (Version control and rollback plans)

Is it hard to build decks because you have to move cards from deck to the next all the time, or your decks shares a lot of cards between them? (Dependencies)

Do you feel comfortable with your sideboard, knowing what to board in and out in most matchups? What could go wrong? (Risk analysis)

Constructed: Undead Party Crasher

Top8 Draft: URb Control

93/94 Sligh