1.
Requirements are the foundation of the entire testing process and should describe in detail
what needs to be solved or achieved to meet the objectives of your application under
development.
2. you use the requirements data during the Plan Tests stage to create tests for testing the
requirements.
3. Execute the Tests stage; you execute these tests to check whether the requirements have been
met.
4. In the Track Defects stage, you log and track defects to ensure that the final product contains no
errors.
5. Requirements Tree – This enables you to view your requirements hierarchically in a tree.
6. Traceability Matrix lets you view traceability relationships between requirements and other
requirements or tests in a matrix.
7. A Requirement tree is a visual organization of the relationship between requirements.
8. Target Cycle – Indicates the cycle to which the requirement is assigned.
9. History – Displays a list of changes made to the currently selected requirement
10. Relationships – Enables you to add and remove traceability links between requirements
11. A low value can imply that the source requirement is not associated with enough requirements
or tests.
12. The Drill Down Results window displays a list of requirements in the risk category.
13. ALI is embedded in ALM to aggregate information from multiple development tools and to
establish complete ALM traceability.
14. The third stage of the testing process is test planning.
15. good test plan enables you to assess the quality of your application at any point in the
application management process.
16. The Test Plan module enables you to divide your application according to functionality.
17. Test Plan This is a graphical representation of your test plan, displaying your tests according to
the hierarchical relationship of their functions.
18. The Test Plan tree: Organizes tests according to an application's functional units or subjects.
Provides a clear picture of the testing building blocks and assists in the development of actual
tests. Shows the hierarchical relationships and dependencies between tests
19. Tree requirements, the requirements are used to define your test plan in the Test Plan module.
20. Convert To Test – Converts the selected requirement to a test
21. Convert To Step – Converts the selected requirement to a test step
22. Economical – A test must include only the necessary steps and fields.
23. Accurate – Each test should have a distinct objective, such as verifying a specific function or
system requirement.
24. A parameter is a variable that can be assigned a value during test execution.
25. A test script contains the actions to perform during test execution.
26. You can design tests that run according to different use cases, each with other data sets. Each
use case is called a test configuration.
27. A live analysis graph provides a visual overview of all the tests within a folder in the test Plan
tree.
28. The fourth stage of the application lifecycle management process involves organizing tests into
test sets and running the tests.
29. A test set is a group of tests designed to achieve specific testing goals.
30. The goals of a test set must synchronize with the testing goals of the release to which it is
assigned.
31. Developing a Test Sets tree helps you organize your testing process by grouping test sets into
folders and organizing the folders in different hierarchical levels.
32. Tests in Functional test sets are run using server-side execution. This means you do not have to
be around to initiate and control the tests.
33. Open Date – Displays the planned start date for the test set.
34. A test set can include any single test configuration, the entire test configurations defined for a
test, or it can consist of test configurations based on requirement coverage.
35. A test set folder contains tests that you can assign to cycles in the Management module.
36. The Test Runs module allows you to view all test runs for your project in a grid.
37. Testing is shifting to adopt Agile and Continuous Integration methodologies.
38. Sprinter provides advanced functionality and tools to make manual testing more efficient and
effective.
39. Sprinter enables you to accomplish these tasks without disrupting your test flow.
40. Sprinter can learn your application's display and identify its objects.
41. With mirroring, every user action you perform in your application on your primary machine is
replicated on the defined secondary machines.
42. Web standards scanner – This scanner checks that the web page complies with web standards
for HTML validity, as defined by the World Wide Web Consortium (W3C).
43. Custom scanner – Sprinter allows you to extend the scanner’s capabilities by defining custom
scanners.
44. Spell check scanner – This scanner checks your application for spelling errors.
45. With Power mode enabled, you can navigate your application without following predefined
steps.
46. The Scan Results Viewer also enables you to address the results by submitting defects to ALM
based on the results.
47. The Centered box is the handset itself, a real one; when you perform actions, those actions are
being executed on the device.
48. The Data Injection Status dialog box is displayed and shows the status.
49. Broken links scanner – This scanner is relevant only for web applications and checks your
application for broken hyperlinks and missing referenced content. You can set the threshold time
50. Localization scanner – This scanner checks your application for errors resulting from translating
the application’s UI into different languages.
