紫光展锐CtsContactsProviderWipe测试数据库擦除通知

zaqwsx2

问题描述（Issue Description）
[CTS\GTS\VTS…Test Step] :
− cd Android-vts/tools
− vts-tradefed
− run cts-on-gsi -m CtsContactsProviderWipe -t
android.provider.cts.contactsproviderwipe.ContactsContract_Wipe#testDatabaseWipeNotification
− check the VTS test result
[CTS/GTS/VTS Version] : VTS 10_r3
[GMS/GSI Version]: GSI 10_202003
[Security Patch]: Update to 2020-04-05
[Testing Result]:
android.provider.cts.contactsproviderwipe.ContactsContract_Wipe#testDatabaseWipeNotification failed:
junit.Framework.AssertionFailedError: expected:<content://com.android.contacts/provider_status>
but was:<content://com.android.contacts>

问题分析（Analysis）
1. In testDatabaseWipeNotification function, Register an observer class to monitor ProviderStatus.CONTENT_URI.
The second parameter of registerContentObserver is set 'false'. So the observer will be notified whenever a change
occurs to the exact URI specified by <code>uri</code> or to one of the URI's ancestors in the path hierarchy.
2. In this test, ContactsContract.AUTHORITY_URI is changed in ContactsProvider2.notifyChange(). This observer is
notified and ContactsContract.AUTHORITY_URI is transmitted to callback function 'onChange'. And notifiedUri is set as
ContactsContract.AUTHORITY_URI . When execute assertEquals(ProviderStatus.CONTENT_URI, notifiedUri.get()),occur assert error.
3. The observer in this test case monitor ProviderStatus.CONTENT_URI and its ancestors in the path hierarchy. So it is
correct that the value of notifiedUri.get() is ContactsContract.AUTHORITY_URI. So this test case is unreasonable.

问题分析（Analysis）
4. Detailed code as following:

1. //test case
   
2. public void testDatabaseWipeNotification() throws Exception {
   
3. final CountDownLatch latch = new CountDownLatch(1);
   
4. final AtomicReference<Uri> notifiedUri = new AtomicReference<>();
   
5. //register content observer for ProviderStatus.CONTENT_URI
   
6. getContext().getContentResolver().registerContentObserver(ProviderStatus.CONTENT_URI,
   
7. /* notifyForDescendants=*/ false,
   
8. new ContentObserver(new Handler(Looper.getMainLooper())) {
   
9. @Override
   
10. public void onChange(boolean selfChange, Uri uri) { // callback function
    
11. Log.i(TAG, "Received notification on " + uri);
    
12. notifiedUri.set(uri);
    
13. latch.countDown();
    
14. }
    
15. });
    
16. wipeContactsProvider();
    
17. // Accessing CP2 to make sure the process starts.
    
18. getDatabaseCreationTimestamp();
    
19. assertTrue("Didn't receive content change notification",
    
20. latch.await(120, TimeUnit.SECONDS));
    
21. assertEquals(ProviderStatus.CONTENT_URI, notifiedUri.get()); //occur assert
    
22. }

复制代码

1. <p>//packages/providers/ContactsProvider/src/com/android/providers/contacts/ContactsProvider2.java</p><p>protected void notifyChange(boolean syncToNetwork, boolean syncToMetadataNetwork) {</p><p>//ContactsContract.AUTHORITY_URI changed</p><p>getContext().getContentResolver().notifyChange(ContactsContract.AUTHORITY_URI, null,</p><p>syncToNetwork || syncToMetadataNetwork);</p><p>getContext().getContentResolver().notifyChange(MetadataSync.METADATA_AUTHORITY_URI,</p><p>null, syncToMetadataNetwork);</p><p>}</p>

复制代码

	结果	谷歌反馈	信息
谷歌确认此弃权	NA	<apphosting-stubby-api-- s-7egoogle-2ecom- 3agitwatcher@prod.goog le.com> #20Apr 10, 2020 06:43AM Marked as fixed. Project: platform/cts Branch: android10-testsdev	NA

	结果	详情(如果结果是YES)
使用来自 Partner Android Build (PAB) dashboard 的最新 CTS/GSI/VT S dev builds，来验证失败的测试，测试失败不再发生。	YES	Test Date: 2020 April 26 Test Case: run cts-on-gsi -m CtsContactsProviderWipe -t android.provider.cts.contactsproviderwipe.ContactsContract_ Wipe#testDatabaseWipeNotification CTS/VTS/CTS-On-GSI dev Build Number: build#6395341 Build Created date: 2020 April 15

TR_Bug1261433_CtsContactsProviderWipe_testDatabaseWipeNotification、

文件大小:

1 MB

下载次数:

1

附件售价:

2 RD币  

本地下载 立即购买

*附件为作者发布，与本站无关，如有侵权，请联系客服删除