IN_PROC_BROWSER_TEST_F(TabGroupsApiBrowserTest, TabGroupsOnCreated) {This is all cut/paste, with `TEST_F -> IN_PROC_BROWSER_TEST_F`, updating the test suite class name, and switching `browser_context()` to `profile()`. No functional changes.
// Basic API tests for the tabGroups API. Most API behavior is tested inThis file is used by tab_groups_api_apitests.cc, and is an `ExtensionApiTest`, so I updated the comment.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
lgtm!
IN_PROC_BROWSER_TEST_F(TabGroupsApiBrowserTest, TabGroupsOnCreated) {This is all cut/paste, with `TEST_F -> IN_PROC_BROWSER_TEST_F`, updating the test suite class name, and switching `browser_context()` to `profile()`. No functional changes.
Acknowledged
// Basic API tests for the tabGroups API. Most API behavior is tested inThis file is used by tab_groups_api_apitests.cc, and is an `ExtensionApiTest`, so I updated the comment.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
extensions: Port tab group API unit tests to browser tests, part 7
The tab groups API unit test suite provides good coverage, but uses
concepts like Browser and BrowserWindow that are not supposed to be
used anymore in unit tests. (See chrome browser design principles in
//docs or the comment in this browser test file.) Converting to browser
test both fixes this design issue and sets up the tests for future
conversion to run on desktop Android.
This CL cut/pastes over all the remaining tests and deletes the unit
test file.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |