Googletest export
Internal change PiperOrigin-RevId: 378672633
This commit is contained in:
		
				
					committed by
					
						
						Dino Radaković
					
				
			
			
				
	
			
			
			
						parent
						
							3c4b3a039e
						
					
				
				
					commit
					b050d6c4b0
				
			@@ -319,7 +319,7 @@ The above uses both `ASSERT_*` and `EXPECT_*` assertions. The rule of thumb is
 | 
				
			|||||||
to use `EXPECT_*` when you want the test to continue to reveal more errors after
 | 
					to use `EXPECT_*` when you want the test to continue to reveal more errors after
 | 
				
			||||||
the assertion failure, and use `ASSERT_*` when continuing after failure doesn't
 | 
					the assertion failure, and use `ASSERT_*` when continuing after failure doesn't
 | 
				
			||||||
make sense. For example, the second assertion in the `Dequeue` test is
 | 
					make sense. For example, the second assertion in the `Dequeue` test is
 | 
				
			||||||
`ASSERT_NE(nullptr, n)`, as we need to dereference the pointer `n` later, which
 | 
					`ASSERT_NE(n, nullptr)`, as we need to dereference the pointer `n` later, which
 | 
				
			||||||
would lead to a segfault when `n` is `NULL`.
 | 
					would lead to a segfault when `n` is `NULL`.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
When these tests run, the following happens:
 | 
					When these tests run, the following happens:
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user