From 62eddef65bf9521297ec373381befeef7ce67d22 Mon Sep 17 00:00:00 2001
From: Psyyringe <Psyyringe@01922e74-a4c3-11dd-a5cd-697bfd0a0cef>
Date: Sun, 8 Nov 2009 04:59:20 +0000
Subject: [PATCH] Psyringe - added bug test scripts for i159, i160, i161.

---
 .../Res/test/bugs/blocking_modifiers_i160.txt | 44 +++++++++++++++++++
 .../mtg/bin/Res/test/bugs/brass_man_i161.txt  | 36 +++++++++++++++
 .../mtg/bin/Res/test/bugs/stonebrow_i159.txt  | 20 +++++++++
 3 files changed, 100 insertions(+)
 create mode 100644 projects/mtg/bin/Res/test/bugs/blocking_modifiers_i160.txt
 create mode 100644 projects/mtg/bin/Res/test/bugs/brass_man_i161.txt
 create mode 100644 projects/mtg/bin/Res/test/bugs/stonebrow_i159.txt

diff --git a/projects/mtg/bin/Res/test/bugs/blocking_modifiers_i160.txt b/projects/mtg/bin/Res/test/bugs/blocking_modifiers_i160.txt
new file mode 100644
index 000000000..a26f693d8
--- /dev/null
+++ b/projects/mtg/bin/Res/test/bugs/blocking_modifiers_i160.txt
@@ -0,0 +1,44 @@
+#NAME: Blocking modifiers
+#DESC: When using cards like:
+#DESC: auto=target(creature[blocking]) 4/4
+#DESC: then you can put your creature into
+#DESC: "block mode", give it +4/+4, then
+#DESC: remove it from combat - and it will
+#DESC: still have the +4/+4 modifier.
+#DESC: This is tested here with Elven Fortress,
+#DESC: which gives a 0/+1 modifier to a
+#DESC: blocking Grizzly Bears, which is then
+#DESC: removed from blocking. It should go
+#DECK: back to 2/2 now and be killed by Shock.
+[INIT]
+combatattackers
+[PLAYER1]
+inplay:Mountain,Raging Goblin
+hand:Shock
+[PLAYER2]
+inplay:Forest,Plains,Elven Fortress,Grizzly Bears
+life:20
+[DO]
+Raging Goblin
+next
+Grizzly Bears
+Forest
+Plains
+Elven Fortress
+Grizzly Bears
+Grizzly Bears
+next
+Mountain
+Shock
+Grizzly Bears
+[ASSERT]
+combatdamage
+[PLAYER1]
+inplay:Mountain,Raging Goblin
+hand:
+graveyard:Shock
+[PLAYER2]
+inplay:Forest,Plains,Elven Fortress
+graveyard:Grizzly Bears
+life:19
+[END]
diff --git a/projects/mtg/bin/Res/test/bugs/brass_man_i161.txt b/projects/mtg/bin/Res/test/bugs/brass_man_i161.txt
new file mode 100644
index 000000000..4f6e9ebfc
--- /dev/null
+++ b/projects/mtg/bin/Res/test/bugs/brass_man_i161.txt
@@ -0,0 +1,36 @@
+#NAME: Brass Man untapping
+#DESC: Brass Man can untap outside of Upkeep.
+#DESC: To test this, we try to untap him in
+#DESC: secondmain and then cast Assassinate
+#DESC: on him (which should destroy him if
+#DESC: he's still tapped, which he should be).
+[INIT]
+combatattackers
+[PLAYER1]
+inplay:Brass Man,Island,Swamp,Plains,Forest
+hand:Assassinate
+[PLAYER2]
+life:20
+[DO]
+Brass Man
+next
+next
+next
+next
+Island
+Brass Man
+choice 0
+Swamp
+Plains
+Forest
+Assassinate
+Brass Man
+[ASSERT]
+secondmain
+[PLAYER1]
+inplay:Island,Swamp,Plains,Forest
+hand:
+graveyard:Brass Man,Assassinate
+[PLAYER2]
+life:19
+[END]
diff --git a/projects/mtg/bin/Res/test/bugs/stonebrow_i159.txt b/projects/mtg/bin/Res/test/bugs/stonebrow_i159.txt
new file mode 100644
index 000000000..ce61eb366
--- /dev/null
+++ b/projects/mtg/bin/Res/test/bugs/stonebrow_i159.txt
@@ -0,0 +1,20 @@
+#NAME: Stonebrow crash
+#DESC: Summoning Stonebrow, Krosan Hero causes
+#DESC: an access violation.
+#DESC: See http://code.google.com/p/wagic/issues/detail?id=159
+[INIT]
+firstmain
+[PLAYER1]
+hand:118915
+manapool:{R}{R}{R}{R}{G}
+[PLAYER2]
+[DO]
+118915
+[ASSERT]
+firstmain
+[PLAYER1]
+inplay:118915
+hand:
+manapool:
+[PLAYER2]
+[END]