estimate-usage-details-indexeddb.https.tentative.any.js

Enable keyboard shortcuts

This test has a WPT meta file that expects 2 subtest issues.
This WPT test may be referenced by the following Test IDs:
- /storage/estimate-usage-details-indexeddb.https.tentative.any.html - WPT Dashboard Interop Dashboard
- /storage/estimate-usage-details-indexeddb.https.tentative.any.worker.html - WPT Dashboard Interop Dashboard

// META: title=StorageManager: estimate() usage details for indexeddb

// META: script=helpers.js

// META: script=../IndexedDB/resources/support-promises.js

promise_test(async t => {

  const estimate = await navigator.storage.estimate()

  assert_equals(typeof estimate.usageDetails, 'object');

}, 'estimate() resolves to dictionary with usageDetails member');

promise_test(async t => {

  // We use 100KB here because db compaction usually happens every few MB

  // 100KB is large enough to avoid a false positive (small amounts of metadata

  // getting written for some random reason), and small enough to avoid

  // compaction with a reasonably high probability.

  const writeSize = 1024 * 100;

  const objectStoreName = 'store';

  const dbname = self.location.pathname;

  await indexedDB.deleteDatabase(dbname);

  let usageAfterWrite, usageBeforeWrite;

  // TODO(crbug.com/906867): Refactor this test to better deal with db/log

  //                         compaction flakiness

  // The for loop here is to help make this test less flaky.  The reason it is

  // flaky is that database and/or log compaction could happen in the middle of

  // this loop.  The problem is that this test runs in a large batch of tests,

  // and previous tests might have created a lot of garbage which could trigger

  // compaction.  Suppose the initial estimate shows 1MB usage before creating

  // the db.  Compaction could happen after this step and before we measure

  // usage at the end, meaning the 1MB could be wiped to 0, an extra 1024 * 100

  // is put in, and the actual increase in usage does not reach our expected

  // increase.  Loop 10 times here to be safe (and reduce the number of bot

  // builds that fail); all it takes is one iteration without compaction for

  // this to pass.

  for (let i = 0; i < 10; i++) {

    const db = await createDB(dbname, objectStoreName, t);

    let estimate = await navigator.storage.estimate();

    // If usage is 0, usageDetails does not include the usage (undefined)

    usageBeforeWrite = estimate.usageDetails.indexedDB || 0;

    const txn = db.transaction(objectStoreName, 'readwrite');

    const valueToStore = largeValue(writeSize, Math.random() * 255);

    txn.objectStore(objectStoreName).add(valueToStore, 1);

    await transactionPromise(txn);

    estimate = await navigator.storage.estimate();

    usageAfterWrite = estimate.usageDetails.indexedDB;

    db.close();

    if (usageAfterWrite - usageBeforeWrite >= writeSize) {

      break;

  assert_greater_than_equal(usageAfterWrite - usageBeforeWrite,

      writeSize);

}, 'estimate() usage details reflects increase in indexedDB after large ' +

   'value is stored');