From MySQL 5.6.13 change log:

Unlike MyISAM, InnoDB does not support boolean full-text searches on 
nonindexed columns, but this restriction was not enforced, resulting 
in queries that returned incorrect results. (Bug #16434374)

storage/innobase/mysql-test/storage_engine/fulltext_search.rdiff

---- suite/storage_engine/fulltext_search.result	2013-10-03 20:35:06.000000000 +0400
-+++ suite/storage_engine/fulltext_search.reject	2013-11-08 17:46:03.000000000 +0400
+--- suite/storage_engine/fulltext_search.result	2013-11-27 18:50:16.000000000 +0400
++++ suite/storage_engine/fulltext_search.reject	2014-02-05 15:33:26.000000000 +0400
 @@ -52,15 +52,14 @@
  INSERT INTO t1 (v0,v1,v2) VALUES ('text4','Contributing more...','...is a good idea'),('text5','test','test');
  SELECT v0, MATCH(v1) AGAINST('contributing') AS rating FROM t1 WHERE MATCH(v1) AGAINST ('contributing');
@@ -7,10 +7,12 @@
 -text4	1.3705332279205322
 +text4	0.4885590672492981
  SELECT v0 FROM t1 WHERE MATCH(v1,v2) AGAINST ('-test1 +critical +Cook*' IN BOOLEAN MODE);
- v0
+-v0
 -text1
++ERROR HY000: Can't find FULLTEXT index matching the column list
  SELECT v0 FROM t1 WHERE MATCH(v1,v2) AGAINST ('-patch +critical +Cook*' IN BOOLEAN MODE);
- v0
+-v0
++ERROR HY000: Can't find FULLTEXT index matching the column list
  SELECT v0, MATCH(v1) AGAINST('database' WITH QUERY EXPANSION) AS rating FROM t1 WHERE MATCH(v1) AGAINST ('database' WITH QUERY EXPANSION);
  v0	rating
 -text1	178.11756896972656
@@ -42,6 +44,6 @@
  v0	rating
 -text1	190.56150817871094
 -text4	1.1758291721343994
-+text1	229.6087646484375
++text1	229.60874938964844
 +text4	0.31671249866485596
  DROP TABLE t1;