Test Execution

Why is passing all test cycles treated as a project checkpoint rather than just a QA nicety in a Cloud ALM implementation?

A team runs one full test cycle in the realization phase and considers testing done. What is wrong with that assumption?

Which app do testers open to run and document test cases, and where does it live in the Cloud ALM launchpad?

When test cases and test plans are ready, what does a tester see in the Test Execution app, and how do they narrow it to their own work?

Beyond tester and scope, how can you slice test content so a tester only sees, say, cases touching one interface or one sprint?

A tester spends time crafting an elaborate filter in the Test Execution app and wants to pin it for reuse. What limitation stops them?

In the test case list below the filters, what three views can a tester toggle between?

What happens to a manual test case's overall status the moment a tester clicks Execute to open it?

Inside a manual test case, how is the test data organized that the tester works through?

On the Executed Manual Test Actions tab, what do the green and brown lines each tell a test manager?

What are the four values of the Test Case Overall Status field, and what distinguishes Initial from In Progress?

Nine of ten actions in a test case passed and one failed but the rest are unexecuted. What overall status does the case get, and why is that a common surprise?

Where does a test case's Passed or Failed overall status actually come from, and what field lets you filter on the finer outcome?

In the detailed status list, how does Pass differ from Pass with Conditions?

The detailed status list has four Fail variants. When do you pick plain Fail, Fail - Application Issue, Fail - Test Case Correctness, or Fail - Retest Required?

Which analysis tab compares testing progress across scopes and test plans, and how do you switch between those two breakdowns?

While executing a test case, how can a tester see every change made during that run?

How does a tester launch an automated test case, and how do they narrow the list to only automated ones?

A team wants Cloud ALM to run their automated regression suite overnight on a schedule. Can they, as of April 2024?

After an automated test runs, its status in Cloud ALM looks stale. Why, and how do you get the real status plus per-activity detail?

A tester kicks off an automated test case from inside the test automation provider instead of Cloud ALM. What breaks about the results?

What is the test execution analysis dashboard for, and which role relies on it?

A test manager spots a worrying case in the analytics and tries to click through to it. Why can't they, and what should they do instead?

A test case spans many application test areas and the tester needs to jump straight to one. What control provides that shortcut?

Walk through what a tester actually does to execute one manual test step and record its outcome.

When reporting a test step result, how do you confirm a good step, and when are comments actually required?

A test step fails during execution. What is the fastest way to turn that failure into a tracked defect?

One step of a manual test case is marked Fail. Does that halt the rest of the test case?

A tester needs to pause a long manual test case and pick it up later. Which buttons handle pausing, resuming, and finishing a run?

Where does a tester see the prior execution history of a specific test case, including who ran it and when?

Which criteria can you filter the test execution analysis by at the top of the dashboard?

Which analysis tab shows overall test-run progress for a project, and how do you change how it's displayed?