How to use getRenderTargetTime method in Playwright Internal

Best JavaScript code snippet using playwright-internal

ReactFiberCompleteWork.new.js

Source: ReactFiberCompleteWork.new.js Github

copy

Full Screen

...1004 }1005 row = row.sibling;1006 }1007 }1008 if (renderState.tail !== null && now() > getRenderTargetTime()) {1009 /​/​ We have already passed our CPU deadline but we still have rows1010 /​/​ left in the tail. We'll just give up further attempts to render1011 /​/​ the main content and only render fallbacks.1012 workInProgress.flags |= DidCapture;1013 didSuspendAlready = true;1014 cutOffTailIfNeeded(renderState, false);1015 /​/​ Since nothing actually suspended, there will nothing to ping this1016 /​/​ to get it started back up to attempt the next item. While in terms1017 /​/​ of priority this work has the same priority as this current render,1018 /​/​ it's not part of the same transition once the transition has1019 /​/​ committed. If it's sync, we still want to yield so that it can be1020 /​/​ painted. Conceptually, this is really the same as pinging.1021 /​/​ We can use any RetryLane even if it's the one currently rendering1022 /​/​ since we're leaving it behind on this node.1023 workInProgress.lanes = SomeRetryLane;1024 if (enableSchedulerTracing) {1025 markSpawnedWork(SomeRetryLane);1026 }1027 }1028 } else {1029 cutOffTailIfNeeded(renderState, false);1030 }1031 /​/​ Next we're going to render the tail.1032 } else {1033 /​/​ Append the rendered row to the child list.1034 if (!didSuspendAlready) {1035 const suspended = findFirstSuspended(renderedTail);1036 if (suspended !== null) {1037 workInProgress.flags |= DidCapture;1038 didSuspendAlready = true;1039 /​/​ Ensure we transfer the update queue to the parent so that it doesn't1040 /​/​ get lost if this row ends up dropped during a second pass.1041 const newThennables = suspended.updateQueue;1042 if (newThennables !== null) {1043 workInProgress.updateQueue = newThennables;1044 workInProgress.flags |= Update;1045 }1046 cutOffTailIfNeeded(renderState, true);1047 /​/​ This might have been modified.1048 if (1049 renderState.tail === null &&1050 renderState.tailMode === 'hidden' &&1051 !renderedTail.alternate &&1052 !getIsHydrating() /​/​ We don't cut it if we're hydrating.1053 ) {1054 /​/​ We need to delete the row we just rendered.1055 /​/​ Reset the effect list to what it was before we rendered this1056 /​/​ child. The nested children have already appended themselves.1057 const lastEffect = (workInProgress.lastEffect =1058 renderState.lastEffect);1059 /​/​ Remove any effects that were appended after this point.1060 if (lastEffect !== null) {1061 lastEffect.nextEffect = null;1062 }1063 /​/​ We're done.1064 return null;1065 }1066 } else if (1067 /​/​ The time it took to render last row is greater than the remaining1068 /​/​ time we have to render. So rendering one more row would likely1069 /​/​ exceed it.1070 now() * 2 - renderState.renderingStartTime >1071 getRenderTargetTime() &&1072 renderLanes !== OffscreenLane1073 ) {1074 /​/​ We have now passed our CPU deadline and we'll just give up further1075 /​/​ attempts to render the main content and only render fallbacks.1076 /​/​ The assumption is that this is usually faster.1077 workInProgress.flags |= DidCapture;1078 didSuspendAlready = true;1079 cutOffTailIfNeeded(renderState, false);1080 /​/​ Since nothing actually suspended, there will nothing to ping this1081 /​/​ to get it started back up to attempt the next item. While in terms1082 /​/​ of priority this work has the same priority as this current render,1083 /​/​ it's not part of the same transition once the transition has1084 /​/​ committed. If it's sync, we still want to yield so that it can be1085 /​/​ painted. Conceptually, this is really the same as pinging....

Full Screen

Full Screen

ReactFiberCompleteWork.js

Source: ReactFiberCompleteWork.js Github

copy

Full Screen

...477 }478 row = row.sibling;479 }480 }481 if (renderState.tail !== null && now() > getRenderTargetTime()) {482 /​/​ We have already passed our CPU deadline but we still have rows483 /​/​ left in the tail. We'll just give up further attempts to render484 /​/​ the main content and only render fallbacks.485 workInProgress.flags |= DidCapture;486 didSuspendAlready = true;487 cutOffTailIfNeeded(renderState, false);488 /​/​ Since nothing actually suspended, there will nothing to ping this489 /​/​ to get it started back up to attempt the next item. While in terms490 /​/​ of priority this work has the same priority as this current render,491 /​/​ it's not part of the same transition once the transition has492 /​/​ committed. If it's sync, we still want to yield so that it can be493 /​/​ painted. Conceptually, this is really the same as pinging.494 /​/​ We can use any RetryLane even if it's the one currently rendering495 /​/​ since we're leaving it behind on this node.496 workInProgress.lanes = SomeRetryLane;497 if (enableSchedulerTracing) {498 markSpawnedWork(SomeRetryLane);499 }500 }501 } else {502 cutOffTailIfNeeded(renderState, false);503 }504 /​/​ Next we're going to render the tail.505 } else {506 /​/​ Append the rendered row to the child list.507 if (!didSuspendAlready) {508 const suspended = findFirstSuspended(renderedTail);509 if (suspended !== null) {510 workInProgress.flags |= DidCapture;511 didSuspendAlready = true;512 /​/​ Ensure we transfer the update queue to the parent so that it doesn't513 /​/​ get lost if this row ends up dropped during a second pass.514 const newThennables = suspended.updateQueue;515 if (newThennables !== null) {516 workInProgress.updateQueue = newThennables;517 workInProgress.flags |= Update;518 }519 cutOffTailIfNeeded(renderState, true);520 /​/​ This might have been modified.521 if (522 renderState.tail === null &&523 renderState.tailMode === "hidden" &&524 !renderedTail.alternate &&525 !getIsHydrating() /​/​ We don't cut it if we're hydrating.526 ) {527 /​/​ We need to delete the row we just rendered.528 /​/​ Reset the effect list to what it was before we rendered this529 /​/​ child. The nested children have already appended themselves.530 const lastEffect = (workInProgress.lastEffect =531 renderState.lastEffect);532 /​/​ Remove any effects that were appended after this point.533 if (lastEffect !== null) {534 lastEffect.nextEffect = null;535 }536 /​/​ We're done.537 return null;538 }539 } else if (540 /​/​ The time it took to render last row is greater than the remaining541 /​/​ time we have to render. So rendering one more row would likely542 /​/​ exceed it.543 now() * 2 - renderState.renderingStartTime >544 getRenderTargetTime() &&545 renderLanes !== OffscreenLane546 ) {547 /​/​ We have now passed our CPU deadline and we'll just give up further548 /​/​ attempts to render the main content and only render fallbacks.549 /​/​ The assumption is that this is usually faster.550 workInProgress.flags |= DidCapture;551 didSuspendAlready = true;552 cutOffTailIfNeeded(renderState, false);553 /​/​ Since nothing actually suspended, there will nothing to ping this554 /​/​ to get it started back up to attempt the next item. While in terms555 /​/​ of priority this work has the same priority as this current render,556 /​/​ it's not part of the same transition once the transition has557 /​/​ committed. If it's sync, we still want to yield so that it can be558 /​/​ painted. Conceptually, this is really the same as pinging....

Full Screen

Full Screen

ReactFiberCompleteWork.old.js

Source: ReactFiberCompleteWork.old.js Github

copy

Full Screen

...439 }440 row = row.sibling;441 }442 }443 if (renderState.tail !== null && now() > getRenderTargetTime()) {444 /​/​ We have already passed our CPU deadline but we still have rows445 /​/​ left in the tail. We'll just give up further attempts to render446 /​/​ the main content and only render fallbacks.447 workInProgress.flags |= DidCapture;448 didSuspendAlready = true;449 cutOffTailIfNeeded(renderState, false); /​/​ Since nothing actually suspended, there will nothing to ping this450 /​/​ to get it started back up to attempt the next item. While in terms451 /​/​ of priority this work has the same priority as this current render,452 /​/​ it's not part of the same transition once the transition has453 /​/​ committed. If it's sync, we still want to yield so that it can be454 /​/​ painted. Conceptually, this is really the same as pinging.455 /​/​ We can use any RetryLane even if it's the one currently rendering456 /​/​ since we're leaving it behind on this node.457 workInProgress.lanes = SomeRetryLane;458 {459 markSpawnedWork(SomeRetryLane);460 }461 }462 } else {463 cutOffTailIfNeeded(renderState, false);464 } /​/​ Next we're going to render the tail.465 } else {466 /​/​ Append the rendered row to the child list.467 if (!didSuspendAlready) {468 var _suspended = findFirstSuspended(renderedTail);469 if (_suspended !== null) {470 workInProgress.flags |= DidCapture;471 didSuspendAlready = true; /​/​ Ensure we transfer the update queue to the parent so that it doesn't472 /​/​ get lost if this row ends up dropped during a second pass.473 var _newThennables = _suspended.updateQueue;474 if (_newThennables !== null) {475 workInProgress.updateQueue = _newThennables;476 workInProgress.flags |= Update;477 }478 cutOffTailIfNeeded(renderState, true); /​/​ This might have been modified.479 if (renderState.tail === null && renderState.tailMode === 'hidden' && !renderedTail.alternate && !getIsHydrating() /​/​ We don't cut it if we're hydrating.480 ) {481 /​/​ We need to delete the row we just rendered.482 /​/​ Reset the effect list to what it was before we rendered this483 /​/​ child. The nested children have already appended themselves.484 var lastEffect = workInProgress.lastEffect = renderState.lastEffect; /​/​ Remove any effects that were appended after this point.485 if (lastEffect !== null) {486 lastEffect.nextEffect = null;487 } /​/​ We're done.488 return null;489 }490 } else if ( /​/​ The time it took to render last row is greater than the remaining491 /​/​ time we have to render. So rendering one more row would likely492 /​/​ exceed it.493 now() * 2 - renderState.renderingStartTime > getRenderTargetTime() && renderLanes !== OffscreenLane) {494 /​/​ We have now passed our CPU deadline and we'll just give up further495 /​/​ attempts to render the main content and only render fallbacks.496 /​/​ The assumption is that this is usually faster.497 workInProgress.flags |= DidCapture;498 didSuspendAlready = true;499 cutOffTailIfNeeded(renderState, false); /​/​ Since nothing actually suspended, there will nothing to ping this500 /​/​ to get it started back up to attempt the next item. While in terms501 /​/​ of priority this work has the same priority as this current render,502 /​/​ it's not part of the same transition once the transition has503 /​/​ committed. If it's sync, we still want to yield so that it can be504 /​/​ painted. Conceptually, this is really the same as pinging.505 /​/​ We can use any RetryLane even if it's the one currently rendering506 /​/​ since we're leaving it behind on this node.507 workInProgress.lanes = SomeRetryLane;...

Full Screen

Full Screen

Using AI Code Generation

copy

Full Screen

1const { chromium } = require('playwright');2(async () => {3 const browser = await chromium.launch();4 const context = await browser.newContext();5 const page = await context.newPage();6 await page.screenshot({ path: 'example.png' });7 const time = await page._getRenderTargetTime();8 console.log(time);9 await browser.close();10})();11const { chromium } = require('playwright');12(async () => {13 const browser = await chromium.launch();14 const context = await browser.newContext();15 const page = await context.newPage();16 await page.screenshot({ path: 'example.png' });17 const time = await page._getRenderTargetTime();18 console.log(time);19 await browser.close();20})();21const { chromium } = require('playwright');22(async () => {23 const browser = await chromium.launch();24 const context = await browser.newContext();25 const page = await context.newPage();26 await page.screenshot({ path: 'example.png' });27 const time = await page._getRenderTargetTime();28 console.log(time);29 await browser.close();30})();31const { chromium } = require('playwright');32(async () => {33 const browser = await chromium.launch();34 const context = await browser.newContext();35 const page = await context.newPage();36 await page.screenshot({ path: 'example.png' });37 const time = await page._getRenderTargetTime();38 console.log(time);39 await browser.close();40})();41const { chromium } = require('playwright');42(async () => {43 const browser = await chromium.launch();44 const context = await browser.newContext();45 const page = await context.newPage();46 await page.screenshot({ path: 'example.png' });

Full Screen

Using AI Code Generation

copy

Full Screen

1const playwright = require('playwright');2(async () => {3 const browser = await playwright.chromium.launch();4 const context = await browser.newContext();5 const page = await context.newPage();6 const time = await page.evaluate(() => window.playwright.getRenderTargetTime());7 console.log(time);8 await browser.close();9})();

Full Screen

Using AI Code Generation

copy

Full Screen

1const playwright = require('playwright');2(async () => {3 const browser = await playwright.chromium.launch();4 const context = await browser.newContext();5 const page = await context.newPage();6 const time = await page.evaluate(() => window.playwright.getRenderTargetTime());7 console.log(time);8 await browser.close();9})();

Full Screen

Using AI Code Generation

copy

Full Screen

1const playwright = require('playwright');2(async () => {3 const browser = await playwright.chromium.launch();4 const context = await browser.newContext();5 const page = await context.newPage();6 const time = await page.evaluate(() => window.playwright.getRenderTargetTime(0));7 console.log(time);8 await browser.close();9})();

Full Screen

Using AI Code Generation

copy

Full Screen

1const playwright = require('playwright');2(async () => {3 const browser = await playwright.chromium.launch();4 const context = await browser.newContext();5 const page = await context.newPage();6 const time = page.getRenderTargetTime();7 console.log(time);8 await browser.close();9})();

Full Screen

Using AI Code Generation

copy

Full Screen

1const { chromium } = require('playwright');2(async () => {3 const browser = await chromium.launch();4 const context = await browser.newContext();5 const page = await context.newPage();6 const target = await page.context().newPage();7 const time = await target.getRenderTargetTime();8 console.log(time);9 await browser.close();10})();11Page.setExtraHTTPHeaders()12Page.setGeolocation()13Page.setHTTPCredentials()14Page.setOfflineMode()15Page.setPermissions()16Page.setExtraHTTPHeaders()17Page.setGeolocation()18Page.setHTTPCredentials()19Page.setOfflineMode()20Page.setPermissions()21Page.setViewportSize()22Page.setContent()23Page.waitForNavigation()24Page.waitForRequest()25Page.waitForResponse()26Page.waitForLoadState()27Page.waitForEvent()28Page.waitForFileChooser()29Page.waitForFunction()30Page.waitForSelector()31Page.waitForTimeout()32Page.waitForURL()33Page.waitForWorker()34Page.waitForEvent()35Page.waitForFileChooser()36Page.waitForFunction()37Page.waitForSelector()38Page.waitForTimeout()39Page.waitForURL()40Page.waitForWorker()

Full Screen

Using AI Code Generation

copy

Full Screen

1const { chromium } = require('playwright');2const { getRenderTargetTime } = require('playwright/​lib/​server/​supplements/​recorder/​recorderSupplement');3(async () => {4 const browser = await chromium.launch();5 const context = await browser.newContext();6 const page = await context.newPage();7 await page.click('text=Get started');8 await page.click('text=Docs');9 await page.click('text=API');10 await page.click('text=Playwright');11 console.log("Render Target Time: ", await getRenderTargetTime(page));12 await browser.close();13})();14const { chromium } = require('playwright');15const { getRenderTargetTime } = require('playwright/​lib/​server/​supplements/​recorder/​recorderSupplement');16(async () => {17 const browser = await chromium.launch();18 const context = await browser.newContext();19 const page = await context.newPage();20 await page.click('text=Get started');21 await page.click('text=Docs');22 await page.click('text=API');23 await page.click('text=Playwright');24 const element = await page.$('text=Playwright');25 console.log("Render Target Time: ", await getRenderTargetTime(page, element));26 await browser.close();27})();28const { chromium } = require('playwright');

Full Screen

Using AI Code Generation

copy

Full Screen

1const playwright = require('playwright');2const { getRenderTargetTime } = require('playwright/​lib/​server/​supplements/​recorder/​recorderSupplement');3(async () => {4 const browser = await playwright['chromium'].launch();5 const context = await browser.newContext();6 const page = await context.newPage();7 const startTime = getRenderTargetTime();8 const endTime = getRenderTargetTime();9 await browser.close();10 console.log(`Time taken to render the page is ${endTime - startTime} ms`);11})();12Your name to display (optional):13Your name to display (optional):14const playwright = require('playwright');15(async () => {16 const browser = await playwright['chromium'].launch();17 const context = await browser.newContext();18 const page = await context.newPage();19 const startTime = Date.now();20 const endTime = Date.now();21 await browser.close();22 console.log(`Time taken to render the page is ${endTime - startTime} ms`);23})();24Your name to display (optional):25Your name to display (optional):26const playwright = require('playwright');27(async () => {28 const browser = await playwright['chromium'].launch();29 const context = await browser.newContext();30 const page = await context.newPage();31 const startTime = Date.now();32 const endTime = Date.now();33 await browser.close();34 console.log(`Time taken to render the page is ${endTime - startTime} ms`);35})();36Your name to display (optional):37Your name to display (optional):38const playwright = require('playwright');39(async () => {40 const browser = await playwright['chromium'].launch();

Full Screen

Using AI Code Generation

copy

Full Screen

1const playwright = require('playwright');2(async () => {3 const browser = await playwright.webkit.launch({ headless: false });4 const context = await browser.newContext();5 const page = await context.newPage();6 const rt = await page.getRenderTargetTime();7 console.log(rt);8 await browser.close();9})();10const playwright = require('playwright');11(async () => {12 const browser = await playwright.firefox.launch({ headless: false });13 const context = await browser.newContext();14 const page = await context.newPage();15 const rt = await page.getRenderTargetTime();16 console.log(rt);17 await browser.close();18})();19const playwright = require('playwright');20(async () => {21 const browser = await playwright.chromium.launch({ headless: false });22 const context = await browser.newContext();23 const page = await context.newPage();24 const rt = await page.getRenderTargetTime();25 console.log(rt);26 await browser.close();27})();28const playwright = require('playwright');29(async () => {30 const browser = await playwright.chromium.launch({ headless: false });31 const context = await browser.newContext();32 const page = await context.newPage();33 const rt = await page.getRenderTargetTime();34 console.log(rt);35 await browser.close();36})();37const playwright = require('playwright');38(async () => {39 const browser = await playwright.chromium.launch({ headless: false });40 const context = await browser.newContext();41 const page = await context.newPage();42 const rt = await page.getRenderTargetTime();43 console.log(rt);44 await browser.close();45})();46const playwright = require('playwright');47(async () => {48 const browser = await playwright.chromium.launch({ headless: false });49 const context = await browser.newContext();50 const page = await context.newPage();51 const rt = await page.getRenderTargetTime();52 console.log(rt);53 await browser.close();54})();55const playwright = require('

Full Screen

Using AI Code Generation

copy

Full Screen

1const { getRenderTargetTime } = require('playwright/​lib/​server/​chromium/​crPage');2const chromium = require('playwright/​lib/​server/​chromium/​crBrowser');3const path = require('path');4(async () => {5 const browser = await chromium.launch({ headless: false });6 const context = await browser.newContext();7 const page = await context.newPage();8 const url = path.resolve(__dirname, './​index.html');9 await page.waitForSelector('text=Hello world');10 const time = await getRenderTargetTime(page);11 console.log(time);12 await browser.close();13})();

Full Screen

StackOverFlow community discussions

Questions
Discussion

Jest + Playwright - Test callbacks of event-based DOM library

firefox browser does not start in playwright

Is it possible to get the selector from a locator object in playwright?

How to run a list of test suites in a single file concurrently in jest?

Running Playwright in Azure Function

firefox browser does not start in playwright

This question is quite close to a "need more focus" question. But let's try to give it some focus:

Does Playwright has access to the cPicker object on the page? Does it has access to the window object?

Yes, you can access both cPicker and the window object inside an evaluate call.

Should I trigger the events from the HTML file itself, and in the callbacks, print in the DOM the result, in some dummy-element, and then infer from that dummy element text that the callbacks fired?

Exactly, or you can assign values to a javascript variable:

const cPicker = new ColorPicker({
  onClickOutside(e){
  },
  onInput(color){
    window['color'] = color;
  },
  onChange(color){
    window['result'] = color;
  }
})

And then

it('Should call all callbacks with correct arguments', async() => {
    await page.goto(`http://localhost:5000/tests/visual/basic.html`, {waitUntil:'load'})

    // Wait until the next frame
    await page.evaluate(() => new Promise(requestAnimationFrame))

    // Act
   
    // Assert
    const result = await page.evaluate(() => window['color']);
    // Check the value
})
https://stackoverflow.com/questions/65477895/jest-playwright-test-callbacks-of-event-based-dom-library

Blogs

Check out the latest blogs from LambdaTest on this topic:

Difference Between Web vs Hybrid vs Native Apps

Native apps are developed specifically for one platform. Hence they are fast and deliver superior performance. They can be downloaded from various app stores and are not accessible through browsers.

How To Use driver.FindElement And driver.FindElements In Selenium C#

One of the essential parts when performing automated UI testing, whether using Selenium or another framework, is identifying the correct web elements the tests will interact with. However, if the web elements are not located correctly, you might get NoSuchElementException in Selenium. This would cause a false negative result because we won’t get to the actual functionality check. Instead, our test will fail simply because it failed to interact with the correct element.

Difference Between Web And Mobile Application Testing

Smartphones have changed the way humans interact with technology. Be it travel, fitness, lifestyle, video games, or even services, it’s all just a few touches away (quite literally so). We only need to look at the growing throngs of smartphone or tablet users vs. desktop users to grasp this reality.

Putting Together a Testing Team

As part of one of my consulting efforts, I worked with a mid-sized company that was looking to move toward a more agile manner of developing software. As with any shift in work style, there is some bewilderment and, for some, considerable anxiety. People are being challenged to leave their comfort zones and embrace a continuously changing, dynamic working environment. And, dare I say it, testing may be the most ‘disturbed’ of the software roles in agile development.

Playwright tutorial

LambdaTest’s Playwright tutorial will give you a broader idea about the Playwright automation framework, its unique features, and use cases with examples to exceed your understanding of Playwright testing. This tutorial will give A to Z guidance, from installing the Playwright framework to some best practices and advanced concepts.

Chapters:

  1. What is Playwright : Playwright is comparatively new but has gained good popularity. Get to know some history of the Playwright with some interesting facts connected with it.
  2. How To Install Playwright : Learn in detail about what basic configuration and dependencies are required for installing Playwright and run a test. Get a step-by-step direction for installing the Playwright automation framework.
  3. Playwright Futuristic Features: Launched in 2020, Playwright gained huge popularity quickly because of some obliging features such as Playwright Test Generator and Inspector, Playwright Reporter, Playwright auto-waiting mechanism and etc. Read up on those features to master Playwright testing.
  4. What is Component Testing: Component testing in Playwright is a unique feature that allows a tester to test a single component of a web application without integrating them with other elements. Learn how to perform Component testing on the Playwright automation framework.
  5. Inputs And Buttons In Playwright: Every website has Input boxes and buttons; learn about testing inputs and buttons with different scenarios and examples.
  6. Functions and Selectors in Playwright: Learn how to launch the Chromium browser with Playwright. Also, gain a better understanding of some important functions like “BrowserContext,” which allows you to run multiple browser sessions, and “newPage” which interacts with a page.
  7. Handling Alerts and Dropdowns in Playwright : Playwright interact with different types of alerts and pop-ups, such as simple, confirmation, and prompt, and different types of dropdowns, such as single selector and multi-selector get your hands-on with handling alerts and dropdown in Playright testing.
  8. Playwright vs Puppeteer: Get to know about the difference between two testing frameworks and how they are different than one another, which browsers they support, and what features they provide.
  9. Run Playwright Tests on LambdaTest: Playwright testing with LambdaTest leverages test performance to the utmost. You can run multiple Playwright tests in Parallel with the LammbdaTest test cloud. Get a step-by-step guide to run your Playwright test on the LambdaTest platform.
  10. Playwright Python Tutorial: Playwright automation framework support all major languages such as Python, JavaScript, TypeScript, .NET and etc. However, there are various advantages to Python end-to-end testing with Playwright because of its versatile utility. Get the hang of Playwright python testing with this chapter.
  11. Playwright End To End Testing Tutorial: Get your hands on with Playwright end-to-end testing and learn to use some exciting features such as TraceViewer, Debugging, Networking, Component testing, Visual testing, and many more.
  12. Playwright Video Tutorial: Watch the video tutorials on Playwright testing from experts and get a consecutive in-depth explanation of Playwright automation testing.

Run Playwright Internal automation tests on LambdaTest cloud grid

Perform automation testing on 3000+ real desktop and mobile devices online.

Try LambdaTest Now !!

Get 100 minutes of automation test minutes FREE!!

Next-Gen App & Browser Testing Cloud

Was this article helpful?

Helpful

NotHelpful