Skip to content

Commit 9e5efee

Browse files
authored
emulator: trivial: fix typo in rollback_test.cc (#18)
* emulator: trivial: fix typo in rollback_test.cc * emulator: mechanical formatting fixes.
1 parent 70d0473 commit 9e5efee

1 file changed

Lines changed: 11 additions & 11 deletions

File tree

google/cloud/bigtable/emulator/rollback_test.cc

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -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

@@ -363,7 +363,7 @@ TEST(TransactonRollback, ZeroOrNegativeTimestampHandling) {
363363
}
364364

365365
// Does the SetCell mutation work to set a cell to a specific value?
366-
TEST(TransactonRollback, SetCellBasicFunction) {
366+
TEST(TransactionRollback, SetCellBasicFunction) {
367367
::google::bigtable::admin::v2::Table schema;
368368
::google::bigtable::admin::v2::ColumnFamily column_family;
369369

@@ -396,7 +396,7 @@ TEST(TransactonRollback, SetCellBasicFunction) {
396396
// Test that an old value is correctly restored in a pre-populated
397397
// cell, when one of a set of SetCell mutations fails after the cell
398398
// had been updated with a new value.
399-
TEST(TransactonRollback, TestRestoreValue) {
399+
TEST(TransactionRollback, TestRestoreValue) {
400400
::google::bigtable::admin::v2::Table schema;
401401
::google::bigtable::admin::v2::ColumnFamily column_family;
402402

@@ -459,7 +459,7 @@ TEST(TransactonRollback, TestRestoreValue) {
459459

460460
// Test that a new cell introduced in a chain of SetCell mutations is
461461
// deleted on rollback if a subsequent mutation fails.
462-
TEST(TransactonRollback, DeleteValue) {
462+
TEST(TransactionRollback, DeleteValue) {
463463
::google::bigtable::admin::v2::Table schema;
464464
::google::bigtable::admin::v2::ColumnFamily column_family;
465465

@@ -514,7 +514,7 @@ TEST(TransactonRollback, DeleteValue) {
514514
// column family name that is not in the table schema) then the column
515515
// and any of the cells introduced is deleted in the rollback, but
516516
// that any pre-transaction-attemot data in the row is unaffected.
517-
TEST(TransactonRollback, DeleteColumn) {
517+
TEST(TransactionRollback, DeleteColumn) {
518518
::google::bigtable::admin::v2::Table schema;
519519
::google::bigtable::admin::v2::ColumnFamily column_family;
520520

@@ -563,7 +563,7 @@ TEST(TransactonRollback, DeleteColumn) {
563563
// Test that a chain of SetCell mutations that initially introduces a
564564
// new row, but one of which eventually fails, will end with the whole
565565
// row rolled back.
566-
TEST(TransactonRollback, DeleteRow) {
566+
TEST(TransactionRollback, DeleteRow) {
567567
::google::bigtable::admin::v2::Table schema;
568568
::google::bigtable::admin::v2::ColumnFamily column_family;
569569

@@ -600,7 +600,7 @@ TEST(TransactonRollback, DeleteRow) {
600600
// Does the DeleteFromfamily mutation work to delete a row from a
601601
// specific family and does it rows with the same row key in other
602602
// column families alone?
603-
TEST(TransactonRollback, DeleteFromFamilyBasicFunction) {
603+
TEST(TransactionRollback, DeleteFromFamilyBasicFunction) {
604604
::google::bigtable::admin::v2::Table schema;
605605
::google::bigtable::admin::v2::ColumnFamily column_family;
606606

@@ -649,7 +649,7 @@ TEST(TransactonRollback, DeleteFromFamilyBasicFunction) {
649649

650650
// Test that DeleteFromfamily can be rolled back in case a subsequent
651651
// mutation fails.
652-
TEST(TransactonRollback, DeleteFromFamilyRollback) {
652+
TEST(TransactionRollback, DeleteFromFamilyRollback) {
653653
::google::bigtable::admin::v2::Table schema;
654654
::google::bigtable::admin::v2::ColumnFamily column_family;
655655

@@ -716,7 +716,7 @@ ::google::bigtable::v2::TimestampRange* NewTimestampRange(int64_t start,
716716
}
717717

718718
// Does DeleteFromColumn basically work?
719-
TEST(TransactonRollback, DeleteFromColumnBasicFunction) {
719+
TEST(TransactionRollback, DeleteFromColumnBasicFunction) {
720720
::google::bigtable::admin::v2::Table schema;
721721
::google::bigtable::admin::v2::ColumnFamily column_family;
722722

@@ -758,7 +758,7 @@ TEST(TransactonRollback, DeleteFromColumnBasicFunction) {
758758
}
759759

760760
// Does DeleteFromColumn rollback work?
761-
TEST(TransactonRollback, DeleteFromColumnRollback) {
761+
TEST(TransactionRollback, DeleteFromColumnRollback) {
762762
::google::bigtable::admin::v2::Table schema;
763763
::google::bigtable::admin::v2::ColumnFamily column_family;
764764

@@ -817,7 +817,7 @@ TEST(TransactonRollback, DeleteFromColumnRollback) {
817817
}
818818

819819
// Can we delete a row from all column families?
820-
TEST(TransactonRollback, DeleteFromRowBasicFunction) {
820+
TEST(TransactionRollback, DeleteFromRowBasicFunction) {
821821
::google::bigtable::admin::v2::Table schema;
822822
::google::bigtable::admin::v2::ColumnFamily column_family;
823823

0 commit comments

Comments
 (0)