@@ -273,7 +273,7 @@ Status HasRow(std::shared_ptr<google::cloud::bigtable::emulator::Table>& table,
273273//
274274// Supplied with a timestamp < -1, it should return an error and fail the entire
275275// mutation chain.
276- TEST (TransactonRollback , ZeroOrNegativeTimestampHandling) {
276+ TEST (TransactionRollback , ZeroOrNegativeTimestampHandling) {
277277 ::google::bigtable::admin::v2::Table schema;
278278 ::google::bigtable::admin::v2::ColumnFamily column_family;
279279
@@ -346,12 +346,13 @@ TEST(TransactonRollback, ZeroOrNegativeTimestampHandling) {
346346 {column_family_name, column_qualifier, -1 , data},
347347 };
348348 auto const * const row_key_5 = " 4" ;
349- auto system_time_ms_before = std::chrono::duration_cast<std::chrono::milliseconds>(
350- std::chrono::system_clock::now ().time_since_epoch ());
349+ auto system_time_ms_before =
350+ std::chrono::duration_cast<std::chrono::milliseconds>(
351+ std::chrono::system_clock::now ().time_since_epoch ());
351352 status = SetCells (table, table_name, row_key_5, v);
352353 ASSERT_STATUS_OK (status);
353- auto column_or = GetColumn (
354- table, v[ 0 ]. column_family_name , row_key_5, v[0 ].column_qualifier );
354+ auto column_or = GetColumn (table, v[ 0 ]. column_family_name , row_key_5,
355+ v[0 ].column_qualifier );
355356 ASSERT_STATUS_OK (column_or.status ());
356357 auto col = column_or.value ();
357358 ASSERT_EQ (col.size (), 1 );
@@ -362,7 +363,7 @@ TEST(TransactonRollback, ZeroOrNegativeTimestampHandling) {
362363}
363364
364365// Does the SetCell mutation work to set a cell to a specific value?
365- TEST (TransactonRollback , SetCellBasicFunction) {
366+ TEST (TransactionRollback , SetCellBasicFunction) {
366367 ::google::bigtable::admin::v2::Table schema;
367368 ::google::bigtable::admin::v2::ColumnFamily column_family;
368369
@@ -395,7 +396,7 @@ TEST(TransactonRollback, SetCellBasicFunction) {
395396// Test that an old value is correctly restored in a pre-populated
396397// cell, when one of a set of SetCell mutations fails after the cell
397398// had been updated with a new value.
398- TEST (TransactonRollback , TestRestoreValue) {
399+ TEST (TransactionRollback , TestRestoreValue) {
399400 ::google::bigtable::admin::v2::Table schema;
400401 ::google::bigtable::admin::v2::ColumnFamily column_family;
401402
@@ -458,7 +459,7 @@ TEST(TransactonRollback, TestRestoreValue) {
458459
459460// Test that a new cell introduced in a chain of SetCell mutations is
460461// deleted on rollback if a subsequent mutation fails.
461- TEST (TransactonRollback , DeleteValue) {
462+ TEST (TransactionRollback , DeleteValue) {
462463 ::google::bigtable::admin::v2::Table schema;
463464 ::google::bigtable::admin::v2::ColumnFamily column_family;
464465
@@ -513,7 +514,7 @@ TEST(TransactonRollback, DeleteValue) {
513514// column family name that is not in the table schema) then the column
514515// and any of the cells introduced is deleted in the rollback, but
515516// that any pre-transaction-attemot data in the row is unaffected.
516- TEST (TransactonRollback , DeleteColumn) {
517+ TEST (TransactionRollback , DeleteColumn) {
517518 ::google::bigtable::admin::v2::Table schema;
518519 ::google::bigtable::admin::v2::ColumnFamily column_family;
519520
@@ -562,7 +563,7 @@ TEST(TransactonRollback, DeleteColumn) {
562563// Test that a chain of SetCell mutations that initially introduces a
563564// new row, but one of which eventually fails, will end with the whole
564565// row rolled back.
565- TEST (TransactonRollback , DeleteRow) {
566+ TEST (TransactionRollback , DeleteRow) {
566567 ::google::bigtable::admin::v2::Table schema;
567568 ::google::bigtable::admin::v2::ColumnFamily column_family;
568569
@@ -599,7 +600,7 @@ TEST(TransactonRollback, DeleteRow) {
599600// Does the DeleteFromfamily mutation work to delete a row from a
600601// specific family and does it rows with the same row key in other
601602// column families alone?
602- TEST (TransactonRollback , DeleteFromFamilyBasicFunction) {
603+ TEST (TransactionRollback , DeleteFromFamilyBasicFunction) {
603604 ::google::bigtable::admin::v2::Table schema;
604605 ::google::bigtable::admin::v2::ColumnFamily column_family;
605606
@@ -648,7 +649,7 @@ TEST(TransactonRollback, DeleteFromFamilyBasicFunction) {
648649
649650// Test that DeleteFromfamily can be rolled back in case a subsequent
650651// mutation fails.
651- TEST (TransactonRollback , DeleteFromFamilyRollback) {
652+ TEST (TransactionRollback , DeleteFromFamilyRollback) {
652653 ::google::bigtable::admin::v2::Table schema;
653654 ::google::bigtable::admin::v2::ColumnFamily column_family;
654655
@@ -715,7 +716,7 @@ ::google::bigtable::v2::TimestampRange* NewTimestampRange(int64_t start,
715716}
716717
717718// Does DeleteFromColumn basically work?
718- TEST (TransactonRollback , DeleteFromColumnBasicFunction) {
719+ TEST (TransactionRollback , DeleteFromColumnBasicFunction) {
719720 ::google::bigtable::admin::v2::Table schema;
720721 ::google::bigtable::admin::v2::ColumnFamily column_family;
721722
@@ -757,7 +758,7 @@ TEST(TransactonRollback, DeleteFromColumnBasicFunction) {
757758}
758759
759760// Does DeleteFromColumn rollback work?
760- TEST (TransactonRollback , DeleteFromColumnRollback) {
761+ TEST (TransactionRollback , DeleteFromColumnRollback) {
761762 ::google::bigtable::admin::v2::Table schema;
762763 ::google::bigtable::admin::v2::ColumnFamily column_family;
763764
@@ -816,7 +817,7 @@ TEST(TransactonRollback, DeleteFromColumnRollback) {
816817}
817818
818819// Can we delete a row from all column families?
819- TEST (TransactonRollback , DeleteFromRowBasicFunction) {
820+ TEST (TransactionRollback , DeleteFromRowBasicFunction) {
820821 ::google::bigtable::admin::v2::Table schema;
821822 ::google::bigtable::admin::v2::ColumnFamily column_family;
822823
0 commit comments