change table to unordered list

This commit is contained in:
Pro3757 2023-06-02 00:58:00 +05:30
parent ad1b28b4a9
commit 5ca3ab8331

View File

@ -52,40 +52,38 @@ documentation. We recommend starting with the
More information about building GoogleTest can be found at More information about building GoogleTest can be found at
[googletest/README.md](googletest/README.md). [googletest/README.md](googletest/README.md).
| Feature | Description | ## Features
| ---------------------------- | --------------------------------------------- | * xUnit test framework:
| xUnit test framework | Googletest is based on the | Googletest is based on the [xUnit](https\://en.wikipedia.org/wiki/XUnit)
| | [xUnit](https\://en.wikipedia.org/wiki/XUnit) | testing framework, a popular architecture for unit testing
| | testing framework, a popular architecture for | * Test discovery:
| | unit testing | Googletest automatically discovers and runs your tests, eliminating the need
| Test discovery | Googletest automatically discovers and runs | to manually register your tests
| | your tests, eliminating the need to manually | * Rich set of assertions:
| | register your tests | Googletest provides a variety of assertions, such as equality, inequality,
| Rich set of assertions | Googletest provides a variety of assertions, | exceptions, and more, making it easy to test your code
| | such as equality, inequality, exceptions, and | * User-defined assertions:
| | more, making it easy to test your code | You can define your own assertions with Googletest, making it simple to
| User-defined assertions | You can define your own assertions with | write tests that are specific to your code
| | Googletest, making it simple to write tests | * Death tests:
| | that are specific to your code | Googletest supports death tests, which verify that your code exits in a
| Death tests | Googletest supports death tests, which verify | certain way, making it useful for testing error-handling code
| | that your code exits in a certain way, making | * Fatal and non-fatal failures:
| | it useful for testing error-handling code | You can specify whether a test failure should be treated as fatal or
| Fatal and non-fatal failures | You can specify whether a test failure should | non-fatal with Googletest, allowing tests to continue running even if a
| | be treated as fatal or non-fatal with | failure occurs
| | Googletest, allowing tests to continue | * Value-parameterized tests:
| | running even if a failure occurs | Googletest supports value-parameterized tests, which run multiple times with
| Value-parameterized tests | Googletest supports value-parameterized | different input values, making it useful for testing functions that take
| | tests, which run multiple times with | different inputs
| | different input values, making it useful for | * Type-parameterized tests:
| | testing functions that take different inputs | Googletest also supports type-parameterized tests, which run with different
| Type-parameterized tests | Googletest also supports type-parameterized | data types, making it useful for testing functions that work with different
| | tests, which run with different data types, | data types
| | making it useful for testing functions that | * Various options for running tests:
| | work with different data types | Googletest provides many options for running tests including running
| Various options for running | Googletest provides many options for running | individual tests, running tests in a specific order, and running tests in
| tests | tests, including running individual tests, | parallel
| | running tests in a specific order, and |
| | running tests in parallel |
## Supported Platforms ## Supported Platforms