Migrated several tests from blink to V8 repository.

test/webkit/toString-for-var-decl-expected.txt

Index: test/webkit/toString-for-var-decl-expected.txt
diff --git a/test/webkit/concat-while-having-a-bad-time-expected.txt b/test/webkit/toString-for-var-decl-expected.txt
similarity index 79%
copy from test/webkit/concat-while-having-a-bad-time-expected.txt
copy to test/webkit/toString-for-var-decl-expected.txt
index f949db98fd7b911d30b20281c82ee0f801405c77..e1d7428d18acf5eeb569b7a31712b919c0c15c69 100644
--- a/test/webkit/concat-while-having-a-bad-time-expected.txt
+++ b/test/webkit/toString-for-var-decl-expected.txt
@@ -21,12 +21,16 @@
 # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
-Tests the behavior of Array.prototype.concat while the array is having a bad time due to one of the elements we are concatenating.
+This test checks for a couple of specific ways that bugs in toString() round trips have changed the meanings of functions with var declarations inside for loops.
 
 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
 
 
-PASS [42].concat() is [42]
+PASS unevalf(eval(unevalf(f1))) is unevalf(f1)
+PASS unevalf(eval(unevalf(f2))) is unevalf(f2)
+PASS unevalf(eval(unevalf(f3))) is unevalf(f3)
+PASS unevalf(eval(unevalf(f4))) is unevalf(f4)
+PASS unevalf(f2) != unevalf(f3) is true
 PASS successfullyParsed is true
 
 TEST COMPLETE