OLD | NEW |
1 This directory contains tests for chrome extension activity logging. | 1 This directory contains tests for chrome extension activity logging. |
2 | 2 |
3 The tests use two chrome extensions: | 3 The tests use two chrome extensions: |
4 -test : sends messages to the friend extension and listens for activity | 4 -test : sends messages to the friend extension and listens for activity |
5 logged by the friend extension. Checks the activity has been logged | 5 logged by the friend extension. Checks the activity has been logged |
6 correctly. | 6 correctly. |
7 -friend: recieves messages from the extension and runs a function based on | 7 -friend: recieves messages from the extension and runs a function based on |
8 the contents of the message. | 8 the contents of the message. |
9 | 9 |
10 | 10 |
(...skipping 36 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
47 'my_function_call_id', | 47 'my_function_call_id', |
48 function response() { }); | 48 function response() { }); |
49 }, | 49 }, |
50 expected_activity: ['api.call1', 'api.call2', 'api.call3'] | 50 expected_activity: ['api.call1', 'api.call2', 'api.call3'] |
51 }); | 51 }); |
52 | 52 |
53 where 'my_function_call_id' is the key you added to the fn_map in | 53 where 'my_function_call_id' is the key you added to the fn_map in |
54 reply.js. | 54 reply.js. |
55 | 55 |
56 | 56 |
| 57 Running a testcase in Incognito mode: |
| 58 |
| 59 To check logging when run in incognito mode, add the following to the |
| 60 testcase: |
| 61 |
| 62 is_incognito: true |
| 63 |
| 64 This will automatically cause all new tabs to be opened in incognito mode and |
| 65 check the url information has been correctly cleaned. |
| 66 |
| 67 |
| 68 Configuring a testcase for a particular OS: |
| 69 |
| 70 If you need to disable a test for a particular OS then you can do this by |
| 71 adding the disabled field to the test case. For example: |
| 72 |
| 73 disabled: {win: true, mac: true} |
| 74 |
| 75 If you need to configure different expected activity for a particular OS, you |
| 76 can override the logging. E.g.: |
| 77 |
| 78 expected_activity_win: ['api.call1', 'api.call2', 'api.call3'] |
| 79 expected_activity_mac: ['api.call1', 'api.call2', 'api.call3'] |
| 80 |
| 81 See the chrome.runtime.getPlatformInfo documentation for details of which OS |
| 82 names to use. |
| 83 |
| 84 |
57 Running the tests: | 85 Running the tests: |
58 | 86 |
59 > out/Debug/browser_tests --gtest_filter=ActivityLogApiTest.TriggerEvent | 87 > out/Debug/browser_tests --gtest_filter=ActivityLogApiTest.TriggerEvent |
60 | 88 |
61 | 89 |
62 Running in manual mode: | 90 Running in manual mode: |
63 | 91 |
64 (1) Start chrome with out/Debug/chrome | 92 (1) Start chrome with out/Debug/chrome |
65 (2) Navigate to chrome://extensions | 93 (2) Navigate to chrome://extensions |
66 (3) Install the friend and test extensions from your chrome src folder | 94 (3) Install the friend and test extensions from your chrome src folder |
67 (4) Click on the "options" link under the friend extension | 95 (4) Click on the "options" link under the friend extension |
68 (5) You should see the options page the buttons to run the functions manually | 96 (5) You should see the options page the buttons to run the functions manually |
OLD | NEW |