Telerik Test Studio Tip: Use Element repository as much as you can

Even though we can achieve  same test step without using Element repository, I would really suggest to use Element repository while writing test steps. Telerik Test studio provides powerful global Element repository with nice UI.  Nowadays every IT industry is moving towards Agile Methodology to develop modern web applications causing rapid changes in the applications in frequent manner leading to changes in the UI Elements day by day. It is tremendous pain for test case developer to update all test cases with updated Elements. In Element repository, an option will be provided to Edit elements which will take care of editing in all test cases where element exists. It will also provide an option to validate elements, where automation developers can understand all the elements that are changed in the UI in a single click instead of finding from failure reports after test cases are executed. Thus, user can directly go to that element and update it and it will reduce maintenance time for test cases drastically. In the same way it will provide a lot of options like Rename, Used by etc. where single change will effect in all test cases. I would also like to highlight that all the function which will work on repository element might not work on element  which we identified through coded step. As an example, assume we have SubmitButton in Element repository. Then:

Pages.PageName.SubmitButton.wait.forExists(3000);

will work perfectly but will not work if we write as below.

 <HtmlButton> submitbtn = ActiveBrowser.Find.byName<HtmlButton>(“submit”);

Submitbtn.wait.ForExists(3000);

What is Nagios

Why Monitoring Systems?

Monitoring systems are important to avoid adverse situations that can ensure that preventive checks could be took before the entire IT network crashed leading to direct business loss. Most of the reputable IT consulting firms emphasize on consistent monitoring of your system to ensure that everything is working as it

When I participated in PUG held in America, I have attended Nagios session and found interesting. So here are my findings.

What is Nagios
Nagios is a monitoring tool which mainly helps IT administrators to track problems before they affect critical business processes.It helps you to ensure that your critical systems, applications and services are always up and running. It provides features such as alerting, event handling and reporting.

Why Nagios
OpenSource Tool
Huge number of plugins are already available
On top of that we can build our own plugins
Runs on many Operating Systems

Common things that Nagios can monitor
1. See if server is UP and running
2. Notify if a server is down
3. Will check if service is running such as HTTP, NTP, POP3, IMAP, SMTP, Mail, TELNET etc.
4. Will check if a process or windows service is running
5. Alerts can be configured to go to particular groups/indiduals
6. Will monitor Database Servers such as Oracle, Progress Openedge, Postgres, MYSQL etc.

Different components of Nagios
Nagios Core - This is the heart of the application that contains the core monitoring engine and a basic web UI. And it is supported only on Linux/Unix machines
Nagios Plugins - On top of the Nagios Core, we can implement plugins that will allow us to monitor hosts, devices, services, protocols, and applications.
Nagios Frontend - for enhancing Nagios experience with Themes, web interfaces, mobile interfaces
Nagios Addon Projects - for extending the core functionality provided by a basic Nagios. Examples - NRPE,NCPA etc.


Nagios can also help QA team and below are some of the links which talks about it
http://n8v.enteuxis.org/2011/06/integrating-nagios-with-test-driven-development/
https://exchange.nagios.org/directory/Documentation/Nagios-XI-Documentation/Integrating-Selenium-with-Nagios-XI/details

Want to try Nagios you can download from here