Understanding Menu options in UFT 11.5: Questions and Answers

This is first of the topics in understanding about menu options changes in UFT 11.5 with subjective questions and multiple choice questions. We will discuss various questions based on menu options in UFT 11.5.

Question 1: What are the various menus in UFT 11.5 GUI Test?

Answer: The various menus with important functions in UFT 11.5 are as follows:

· File Menu: The file menu provides commands to:

o   Create New Business Component, Function Library, Solution, test, and Application Area.

o   Open existing Business Component, Function Library, Solution, test, and Application Area.

o   Add existing Business Component, test, and Application Area.

o   Save, Close, and view recent tests and other assets.

·Edit Menu: Provides option to edit content of test including cut, copy, delete, undo and redo the changes.

o   Provides option to format the test using comments, uncomment, using with statements

o   Inserting code snippets

·View Menu: Provides various options to view test information :

o   Viewing toolbox, solutions explorer, properties, test flow, and bookmarks

o   Viewing Data pane, debug information in watch, variable, command window

o   Move from keyword view to editor view  and vice versa

·Search: To search content including text and bookmarks

·Design: Design provides option to design the test with actions, checkpoint , step generator ,and function definition generator:

o   Inserting call to new action, call to existing action, call to copy of action, and call to existing API Test.

o   Enhancing test/action with function definition generator, checkpoints, output value and transaction steps.

o   Validating syntax in the code

Record: Provide option for various recording modes, web event recording configuration settings, and record and run setting

Run: provides various option to run a test with run test, run now, Maintenance run mode, update run mode

o   Runs a test from step, step into, step over, debug from step, run to step.

o   Inserting a variable, object to watch, inserting and removing breakpoints

Resources: provides option to view object repository, object repository manager, Associate repository with an action, mapping repository parameters and creating recovery scenarios.

ALM: Provides options to create connections with ALM/QC and versioning feature of resources From ALM

Tools: Provides various tools and options to work with UFT11.5.

o   Provides tools including object spy, .Net Windows Forms spy, Object Identification, regular expression evaluator, data driver, change active screen, extensibility accelerator and virtual objects.

o   Import WSDL, Import .NET Assembly, rest services

o   Defines tools options for GUI Testing, API Testing, coding, text editor and general options.

Windows: Provide option to move from one window to another.

Help: Provides link to various help, UFT support  and installing license for UFT 11.5

Question 2:  What will happen, if I press Ctrl +Q in a UFT function?

a.       Recovery Scenario Page will open

b.      ALM Connection will open

c.       Object repository

d.      Comment a statement

Answer: Ctrl + Q will open ALM connection window, where we can provide details to connect to ALM Server, project details, and password/username details. To open Object Repository, Press Ctrl + R. To comment a statement, Press Ctrl+M.

Question 3: In which menu, Is regular expression evaluator?

a.     Tools

b.      Edit

c.      View

d.      Resources

Answer: The correct Answer is a) tools

Question 4: Shortcut key to view data table is:

a.       Ctrl+Alt+X

b.      Ctrl+Alt+P

c.       Ctrl+Alt+D

d.      Ctrl+Alt+E

Answer: Shortcut key to view data is Ctrl+Alt+D, Ctrl+Alt+X is shortcut for Toolbox, Ctrl+alt+P for properties, Ctrl+Alt+E for errors and Ctrl+Alt+L for Solution explorer

Question 5: What is the shortcut Key to insert a standard checkpoint?

a.       F9

b.      F10

c.       F11

d.      F12

Answer: F12 is shortcut key for standard Checkpoint, Other Shortcut keys are as follows. F9- Insert/Remove Checkpoints, F10 - Step Over, F11 - Step into, F7 - Step generator.

Some other Useful Shortcut keys are: F6 - Record, F4 - Stop, F5 - Run, Ctrl+F5 - Run from step.

Seven Principles of Software testing

Software Testing focuses on ensuring the quality of the software. Software not tested properly can cause many problems including financial losses, reputation loss and at times injury or even death. How much testing is required depends on the risks associated with the software as well as time constraints. There are few principles of testing that can help to better understand the process of testing and define testing process

The principles of testing are as follows:

1.  Testing shows presence of defect  

Testing helps in uncovering defects although we can never be sure that that there are no defects in the software even after testing. So the focus of testing is to find as many defects in the system.

2.  Exhaustive Testing is not feasible

 Going by the first principle, tester can never be sure that there are no defects in the system, One of the reason for first principle is exhaustive testing is impossible. We can test all the scenarios related to software but the time and resource cost for testing exhaustively will be so huge, it will not bring any value and will not be able to deliver software. Due to this proper risk analysis and priorities of scenarios should be taken care of in testing for balanced and timely testing completion.  Test cases should be prepared based on the functional specification, as test cases for high priority scenario should be executed first.

3.  Testing should start as early as possible

 Catching defects early in the Software development life cycle reduces the cost of fixing of defect. For e.g. Testing should start as early as possible, Reviews should take place to identify gaps in requirements understanding, and identify code issues early.  Also test designing should start as soon as possible.

4.  Most of the Defects are confined to small module

This has been noticed that most of the defects are confined to small module; the reason of defects can be understanding gaps in the particular set of modules and the technical skill of the resources.

5.  Pesticide Paradox

 Executing the same test cases again and again eventually results in no defects being identified by test cases. Due to this reason test cases should be reviewed from time to time, with new test cases added and redundant test cases removed from the regression pack to keep the test suite fresh, up to date and effective. Test cases must include both manual and automated test cases for higher coverage of test scenarios.

6.  Testing requirement varies from software to software 

Testing is done differently for different software. A social networking site will have different requirement of content and performance testing compared to banking software that will require functionality and security as main factors compared to the social networking site. The testing requirements should be well defined in the scope of testing.

7.  The software developed should be usable by user

and should meet user’s need and expectation. It does not matter if there were no defects in testing the software if it does not meet the need of end users.Software 

Understanding Quality Assurance and Quality Control

Whenever a product is delivered to the client, client expects the quality of the end product to be high. To assure high quality of end products, there must be stress on quality. Quality has different meaning for different users. For developer of a product, it means quality of product meets the requirements mentioned in the specifications whereas for end user, it means the product is fit for use and works as expected. A quality Software should possess desired features,should be fit for use and usable at the desired cost

To ensure quality, there are quality Assurance and quality control groups in the organization. In this article, we will discuss the role and difference between quality assurance and quality control.

Quality Assurance

Quality assurance is a planned and systematic set of activities necessary to provide adequate confidence that products and services will conform to specified requirements and meet user needs. The purpose of quality Assurance is to ensure quality policies are defined. The project Quality Assurance must ensure process are implemented for:

•      System development methodologies
•      Estimation processes
•      System maintenance processes
•      Requirements definition processes
•      Testing processes and standards

Quality assurance is a continuous improvement activity in processes uncovering weakness in the process and strengthening the process followed. Normally the quality assurance activities are defined at organization level and are uniformly followed across the project. There are regular audits by an independent QA audit team within organization which audits across different project to ensure Quality assurance activities are followed across the organization.

Quality Control

Quality control is the process in which developed product is compared with requirement at different phases and discrepancy is logged as defects. The process of quality control begins with the development phase. This includes Static testing, and dynamic testing.

Static testing includes reviews and analysis of the code using tools. Reviews include manual examination of the code as well as documentation. Reviews are important to identify gaps early in the development process. Defects detected during reviews early in the life cycle are often much cheaper to remove than those detected while running tests Reviews can vary from informal reviews to formal reviews. Informal reviews, Walkthrough, Technical review, and inspection are all examples of review with varying degree of documentation and formal approach. Static analysis also includes verifying the code effectiveness through code analysis tools.

Once the development of the requirement is completed, the product is passed on to testing team for complete testing. The purpose of testing is to uncover as many defects in the system as possible. The focus of testing is look at the product from different views. A system tester or functional tester will verify the system/functionality is working as per functional requirement. Performance tester will need to verify the performance of system under stress and load conditions and so on. How much testing and what testing is required is normally defined in the scope of testing. There are various test management tools like Quality center that helps to manage and map various test artifacts and defects with test cases.

Quality Assurance and Quality Control activities are required to ensure quality deliverables to client and should be followed religiously to ensure high quality to the customer