Bug#25643748 ASSERT.INC IS MISSING IN FEW GR TESTS

include/assert.inc is missing in following test files added as part of wl9837
    1. gr_savepoint.test
    2. gr_savepoint_crash.test
    3. gr_savepoint_crash_on_release.test
    4. gr_savepoint_crash_on_rollback.test

fix:
added assert.inc in those files.

Author: Dhruthi K V

rapid/plugin/group_replication/tests/mtr/r/gr_savepoint.result

@@ -83,6 +83,7 @@ SET SESSION sql_log_bin= 1;
 ############################################################
 # 11. Cleanup (restore the connection back to original)
 [connection server1]
+include/assert.inc ['Table t1 has values 1 and 2']
 #
 # Don't cause conflict due the rollback and the release don't interfere
 #
@@ -161,6 +162,7 @@ SET SESSION sql_log_bin= 1;
 ############################################################
 # 11. Cleanup (restore the connection back to original)
 [connection server1]
+include/assert.inc ['Table t1 has values 3 and 4']
 #
 # Using SAVEPOINT don't modify the conflict detection
 #
@@ -240,5 +242,8 @@ SET SESSION sql_log_bin= 1;
 ############################################################
 # 11. Cleanup (restore the connection back to original)
 [connection server1]
+include/assert.inc ['There are six values in table t1']
+include/assert.inc ['Table t1 has values 6 and 7']
+include/assert.inc ['Table t1 do not have value 5']
 DROP TABLE t1;
 include/group_replication_end.inc

rapid/plugin/group_replication/tests/mtr/r/gr_savepoint_crash.result

@@ -23,6 +23,7 @@ include/rpl_reconnect.inc
 SET GLOBAL group_replication_force_members= "GROUP_REPLICATION_LOCAL_ADDRESS1";
 [connection server1]
 include/start_group_replication.inc
+include/assert.inc ['There should be two values in table1']
 3. Clean-up
 DROP TABLE table1;
 include/group_replication_end.inc

rapid/plugin/group_replication/tests/mtr/r/gr_savepoint_crash_on_release.result

@@ -29,6 +29,7 @@ SET GLOBAL group_replication_force_members= "GROUP_REPLICATION_LOCAL_ADDRESS1";
 [connection server1]
 include/start_group_replication.inc
 #3. check that incomplete transaction t1 is rolled back, table1 should have only 2 tuples.
+include/assert.inc ['There should be two values in table1']
 #4. Clean-up
 DROP TABLE table1;
 SET @@GLOBAL.DEBUG=@debug_save;

rapid/plugin/group_replication/tests/mtr/r/gr_savepoint_crash_on_rollback.result

@@ -29,6 +29,7 @@ SET GLOBAL group_replication_force_members= "GROUP_REPLICATION_LOCAL_ADDRESS1";
 [connection server1]
 include/start_group_replication.inc
 #3. check that incomplete transaction t1 is rolled back, table1 should have only 2 tuples.
+include/assert.inc ['There should be two values in table1']
 #4. Clean-up
 DROP TABLE table1;
 SET @@GLOBAL.DEBUG=@debug_save;

rapid/plugin/group_replication/tests/mtr/t/gr_savepoint.test

@@ -38,6 +38,7 @@ CREATE TABLE t1(a int primary key);
 
 --let $assert_text= 'Table t1 has values 1 and 2'
 --let $assert_cond= [SELECT COUNT(*) AS count FROM t1 WHERE t1.a = 1 OR t1.a = 2 , count, 1] = 2
+--source include/assert.inc
 
 --echo #
 --echo # Don't cause conflict due the rollback and the release don't interfere
@@ -54,6 +55,7 @@ CREATE TABLE t1(a int primary key);
 
 --let $assert_text= 'Table t1 has values 3 and 4'
 --let $assert_cond= [SELECT COUNT(*) AS count FROM t1 WHERE t1.a = 3 OR t1.a = 4 , count, 1] = 2
+--source include/assert.inc
 
 --echo #
 --echo # Using SAVEPOINT don't modify the conflict detection
@@ -69,12 +71,15 @@ CREATE TABLE t1(a int primary key);
 
 --let $assert_text= 'There are six values in table t1'
 --let $assert_cond= [SELECT COUNT(*) AS count FROM t1, count, 1] = 6
+--source include/assert.inc
 
 --let $assert_text= 'Table t1 has values 6 and 7'
 --let $assert_cond= [SELECT COUNT(*) AS count FROM t1 WHERE t1.a = 6 OR t1.a = 7 , count, 1] = 2
+--source include/assert.inc
 
 --let $assert_text= 'Table t1 do not have value 5'
 --let $assert_cond= [SELECT COUNT(*) AS count FROM t1 WHERE t1.a = 5, count, 1] = 0
+--source include/assert.inc
 
 DROP TABLE t1;
 --source ../inc/group_replication_end.inc

rapid/plugin/group_replication/tests/mtr/t/gr_savepoint_crash.test

@@ -76,6 +76,7 @@ let $wait_condition= SELECT COUNT(*)=2 FROM performance_schema.replication_group
 # check that incomplete transaction t1 is rolled back, table1 should have only 2 tuples.
 --let $assert_text= 'There should be two values in table1'
 --let $assert_cond= [SELECT COUNT(*) AS count FROM table1, count, 1] = 2
+--source include/assert.inc
 
 --echo 3. Clean-up
 DROP TABLE table1;

rapid/plugin/group_replication/tests/mtr/t/gr_savepoint_crash_on_release.test

@@ -95,6 +95,7 @@ let $wait_condition= SELECT COUNT(*)=2 FROM performance_schema.replication_group
 --echo #3. check that incomplete transaction t1 is rolled back, table1 should have only 2 tuples.
 --let $assert_text= 'There should be two values in table1'
 --let $assert_cond= [SELECT COUNT(*) AS count FROM table1, count, 1] = 2
+--source include/assert.inc
 
 --echo #4. Clean-up
 DROP TABLE table1;

rapid/plugin/group_replication/tests/mtr/t/gr_savepoint_crash_on_rollback.test

@@ -95,6 +95,7 @@ let $wait_condition= SELECT COUNT(*)=2 FROM performance_schema.replication_group
 --echo #3. check that incomplete transaction t1 is rolled back, table1 should have only 2 tuples.
 --let $assert_text= 'There should be two values in table1'
 --let $assert_cond= [SELECT COUNT(*) AS count FROM table1, count, 1] = 2
+--source include/assert.inc
 
 --echo #4. Clean-up
 DROP TABLE table1;