Subscribe by Email


Showing posts with label Views. Show all posts
Showing posts with label Views. Show all posts

Wednesday, March 13, 2013

What are characteristics of autonomic system?


Autonomic systems bring both challenges as well as opportunities for the future networking. The increasing numbers of users have had a negative impact on the complexity of the networks; it has also increased by multiple folds. Autonomic systems provide a solution for this problem. 

Characteristics of Autonomic System

  1. High intelligence: These systems have more intelligence incorporated in to them which lets them tackle this increasing complexity easily.
  2. Business Goal: They are driven by the business goal that the quality of experience of the user must be high. Even with the changing environment, there goals remain the same. But there are changes that take place in the low – level configurations. For example, when a user switches over to a low bandwidth network, the bit rate of the video has to be reduced in order to satisfy the goals of the business.
  3. Complex operations: All the operations carried out in an autonomic system are complex in nature even for the simplest of the services. For example, authentication, video encoding, billing, routing, shaping, QoS prioritizing, admission control.
  4. High level objectives: The human operator just has to specify the high – level objectives and it is left to the system whether it chooses to optimize one or more of the goals. In order to achieve this, the system has to translate these objectives in to low – level configurations.
  5. Adaptability: The system has the ability to adapt itself to the current environment.
  6. Policy continuum: There are a number of perspectives to this as mentioned below:
Ø  Business view: Includes guidelines, processes and goals.
Ø  System view: The service should be independent of the technology as well as the device that is being used.
Ø  Network view: It should be specific to technology but independent of the device.
Ø  Device view: Both technology and device specific.
Ø  Instance view: Operation should be specific to an instance.

  1. Elements: The elements of the network are assumed to be heterogeneous by the autonomic communication systems whereas in plain autonomic computing the elements are taken to be as the homogeneous.
  2. Distributed: These systems work up on a distributed environment.
  3. Complexity: The complexity in autonomic systems is more because of the complex autonomic loop that includes the following operations:
Ø  Interaction between the context  and the business goals
Ø  The MAPE (monitor, analyze, plan and execute) loop.

10. Reliability: In autonomic systems, the network has the authority to decide for itself focusing on high level objectives. Autonomic systems rely heavily up on artificial intelligence. However, there are issues associated with artificial intelligence like it becomes difficult to intervene in between when the things go wrong.It is quite difficult to know whether the system is doing the things it is supposed to do or not.
11. Scalability: This is another major characteristic of autonomic systems. It is required to keep track of the large amounts of knowledge and information. Autonomic systems have three tools to take care of this:
Ø Distributed ontologies
Ø Distributed large – scale reasoning
Ø Exchanging only the useful information
ØDistributing information among the different components of the autonomic network.

But in these cases, detection of the conflicts is a difficult task. For handling the various interactions taking place the various autonomic components efficient protocols are required. 
Currently two approaches have been suggested for developing the autonomic networking systems namely:
1. Evolutionary Approach: Incorporating the autonomic behavior in to the pre – existing infrastructure. This approach will consist of updates in increments till a fully autonomic system is developed. This approach is more likely to be adopted even though it requires a lot of patchwork.
2.  Clean slate approach: This approach is focused up on re – designing of the internet.


Wednesday, November 28, 2012

How to generate reports for analyzing the testing process in test director?


Reports and graphs in the test director testing process help you assess up to what extent have your requirements, test runs, test plans, defect tracking etc have progressed.

Generating Reports in Test Director

- In test director you have the facility of generating reports as well as graphs at any point of time in the testing process and from each of the test director modules. 
- You have the choice of working with the default settings as well as the customized ones. 
- While you customize the reports or the graphs you have the right to apply sort conditions as well as filters. 
- Also the information can be displayed according to your specifications if you wish so. 
- The settings you make can be saved as the favorite views and they can be reloaded whenever required. 
- A report can be generated from any of the modules of the test director. 
- Each module of the test director provides you with a variety of report generation options. 
- Once you have generated the report, you can customize various properties of the report as per your wish. 
- The information can be displayed according to your specifications by altering or customizing various properties of that report. 

In this article we shall provide you with the steps for generating a standard requirements report, customizing it for a specific user name and adding it to the favorites list.

Steps for generating reports in Test Director

Follow the steps mentioned below:
  1. First step is to open your project and login. If the project is not open, log on to it.
  2. To view the requirements tree you need to turn on the requirements module. To do so clicking on the requirements tab will display the requirements module.
  3. Next step is to choose a report. To do so go to the analysis option, then reports, and then finally click on the standard requirements report. A report will open up containing the default data.
  4. Next if you need to customize the report as per your needs and specifications.  Clicking on the configure report and sub reports button will launch a report customization page with all the default options already selected.
  5. Here you will get various options for displaying the number of items per display page. Set the option to ‘all items in one page’ if you want them to be displayed all in one page.
  6. If you want to define a filter to view the requirements that were created by a specific user name clicking on the set filter/ sort button will certainly help. A filter dialog box will open up where you will see a filed titled ‘author’. For this click the filter condition box and click on the browse button. This will again open up the select filter condition dialog box. For the users field select the test director log-in user name and click OK. This will close the select the filter condition dialog box. Once again click OK to close the filter dialog box.
  7. Under fields specify the fields and order in which you want them to be displayed. Select the custom field layout and next click on the select fields button to open the select fields dialog box. You will observe the following two fields:
a) Available fields: fields that are not currently displayed.
b) Visible fields: fields that are currently displayed.
You need to select the attachment option in the visible fields box and click the left arrow in order to move it to the available fields. Move the required fields to the available fields box.
  1. Clear the history.
  2. You can add the report as a favorite view by clicking on the add to favorites button.
  3. Close the report. 


Friday, October 5, 2012

Explain the QTP Tool interface?


The tool interface of the quick test professional is the focus of this article. The tool interface of the quick test professional consists of certain elements:
  1. Title bar: This bar displays or holds the name of the test that is currently open.
  2. Menu bar: This bar holds all the quick test commands that one may need often.
  3. File tool bar: This bar holds all the quick test commands or tools that one may need in the management of the tests.
  4. Test tool bar: This bar holds all the quick test commands or tools that may are required in the creation as well as management of the tests.
  5. Debug tool bar: This bar holds all the quick test commands that may be required while debugging of the tests. Usually this bar is not displayed along with the other bars when the quick test professional is launched. If the quick test professional is not displaying the debug bar by default then you need to go to the view and select debug tool bar from the tool bars sub list.
  6. Status bar: This bar displays the current status of the test that is currently under execution.
  7. Action tool bar: This bar holds a list of actions using which one can view the individual details of the whole test flow or an individual test or action. Just like the debug tool bar this tool bar is also not displayed by the quick test professional by default. For displaying it along with the other bars you need to go to the view menu and select action tool bar from the sub list of the tool bars. But if you have inserted an external action or a reusable action in to your test scripts, then the quick test professional displays the action tool bar automatically.
  8. Test pane: This pane consists of two tabs which enable the viewing of the test in two view modes namely: the expert view and the key word view or the tree view.
  9. Test details pane: This pane holds the active screen of the quick test professional.
  10. Data table: This table consists of two tabs namely: the action tab and the global tab. Both of these tabs together provide you assistance during the parameterization of your tests.
  11. Debug viewer pane: This pane consists of three tabs namely, the expressions, the commands and the variables. All of these 3 tabs provide you assistance while you debug your tests. However, there is one issue with debug viewer pane which is that you can open it only when you pause the test run at a break point.
As we know that the quick test professional provides two standard views as well way to modify the test scripts namely:
  1. Key word view and
  2. The expert view
- It is because of these views that the quick test professional is said to possess an IDE or integrated development environment. 
- The quick test professional comes with several standard IDE features like break points etc.
- The scripting language that is used by the quick test professional i.e., the VBScript provides support for the classes but not for the other aspects of object oriented programming like inheritance, polymorphism etc. 
- It lacks some other features such as:
  1. Cannot use some visual basic key words.
  2. Does not have an integrated debugger.
  3. No event handler
  4. No forms editor
- The debugger has got a limited functionality when compared with the debuggers of java, VBA, VB.NET and so on. 


Sunday, September 23, 2012

What is keyword view and Expert view in QTP?


In quick test professional you get two types of views namely the key word view and the expert view which we are going to discuss in this article. 

Keyword View in Quick Test Professional

- The key word view is more like a table like view which consists of a finite number of rows and columns. 
- Each row in the key word view represents a separate step. 
-On the other side, different parts of the steps are marked by the corresponding columns. 
- There is a separate column called the item column which holds the item on which the user wants the step to be carried out. 
- Also, in this column the hierarchy of the GUI object on which the operations are to be carried out. 
- There is another column by the name operation column consisting of the operations to be performed on the item as required. 
- One more column called value column holds the values of the arguments for the operation selected by the user. 
- Each step is documented by the quick test professional under the column titled documentation by the quick test professional for the ease of understanding. 
- The above mentioned 4 columns are the default columns provided by the quick test professional however comment and assignment columns in key word view can be used. 
- With the aid of key word view you can create as well as view the steps of the operation in a tabular, modular and key word driven format. 
- Full access is granted to the test automation experts via some debugging environment and integrated scripting that has round trip synchronizing with the key word view. 

Expert View and Differences between expert and keyword view in Quick Test Professional

- The expert view also displays the same object hierarchy all mapped to the same arguments value and same operation. 
- The basic difference lies between the formats in which the same data is arranged in the two. 
- Both have a distinct way of representing the data though the data displayed is same. 
- All the operations like creation of a step, modifying it and so on can be carried out in the key word view. 
- Expert view as the name suggests is a more advanced way of dealing with the data and requires mastery over the tool. 
- After all of the operations are recorded, they are displayed as steps in the quick test professional in key word view whereas these steps are generated as scripts in the expert view. 
- Expert view is for the advanced testers, using which they can view as well as edit their tests as and when required. 
- This also reveals the underlying standard of the VBscript that is used by the quick test professional. 
- Any changes that are made to the scripts in the expert view are automatically reflected in the key word view also.  
- However, in key word view the exact recording of the applications can be viewed. 
- In key word view, the steps can be created as well as viewed and can be modified by making a selection of the operations as well as items in the key word view and putting in the information as and where required. 
- In the expert view each of the operations that are performed in the form of VB script statements are displayed. 
- There exists a row in the key word view for every method and object. 
- To put it simply, it can be said that the VBscript format is used by the expert view whereas the scripts are represented using graphical user interface which is divided in to 4 default columns as mentioned earlier in the article in key word view. 
- Also, in the expert view all the test statements are displayed.  


Facebook activity