IIS Performance Settings
Blog Home »
*
Calender
May 2009 M T W T F S S
« Apr
1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
*
Recent Posts
o Updates about QTP 10 (I)
o Agent Controller Issue on Starting RAServer Process
o Oracle Tunning
o Bridging the Gap between Open Source & Commercial Tools
o Necessity- the Mother of all Invention (Part II)
*
Archives
o May 2009
o April 2009
o March 2009
o February 2009
o January 2009
o October 2008
o September 2008
o August 2008
o July 2008
*
Tags
Agile Mode CRM | Database Document Object Model | Functional Automation Functional Testing | General General Concepts human resource Human Resources | Open Source Tools Oracle Performance Testing | QTP SRS Telecom Testing
Search Blog
*
Categories
o Catch The Latest
o CRM |
o Functional Automation
o Functional Testing |
o General
o General Concepts
o Human Resources |
o Open Source tools
o Open Source tools
o Other Commercial Tools
o Performance Testing |
o Quick Test Professional
o Rational Functional Tester
o Security Testing
o Telecom Testing
o Testing SOA
o Uncategorized
*
Recent Comments
o Abhay on Sample code to click on dynamic link using Browser DOM
o parul wahi on Testing Ajax Application using QTP
o Pankaj Goel on Testing Ajax Application using QTP
o Pankaj Goel on Oracle Tunning
o Pankaj Goel on Bridging the Gap between Open Source & Commercial Tools
*
Blogger
o Roshi Malhotra
o Kuldeep Singh
o Vaibhav Agarwal
o Rajat Singhal
o Avinash K. Tiwari
o Ravinder Singroha
o Vivek Goyal
o Sudha Sharma
o Betsy Joy
o Shalini Rawal
IIS Performance Settings
July 28th, 2008 admin Posted in Performance Testing | |
By Pankaj Goel
Performance tuning tips for IIS 6.0
The IIS server tuning is slightly involved in terms of understanding the performance critical parameters and tuning them to meet the performance specifications. Some of the ways to improve performance hosted on dot net platform are
a) Recycling Worker process
b) Reducing thread contention
c) Kernel Mode caching
a) Recycling Worker Processes
If a Web application contains code that causes problems, and you cannot easily rewrite the code, it might be useful to limit the extent of the problems by periodically recycling the worker process that services the application. You can accomplish this by using what is known as Worker Process Recycling. Worker process recycling is the replacing of the instance of the application in memory. IIS 6.0 can automatically recycle worker processes by restarting the worker process, or worker processes, that are assigned to an application pool. This helps keep problematic applications running smoothly, and minimizes problems such as memory leaks. You can trigger the recycling of the worker processes assigned to an application pool by using worker process recycling methods that are based on elapsed time, the number of Hypertext Transfer Protocol (HTTP) requests, a set time of day, and two kinds of memory consumption, in addition to recycling on demand.
To configure all the above settings, go to the Properties window of the application pool in which your Web application is running using the IIS manager. Using the Recycling, Performance, and Heal
You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.
AddThis Social Bookmark Button
Leave a Reply
Name (required)
Mail (will not be published) (required)
Website
(Required)
Type the two words:Type what you hear:Incorrect. Try again.
Get a new challenge
Get an audio challengeGet a visual challenge
Help
« SOA Testing Simplified (Series-I)
Telecom Testing »
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
Monday, May 25, 2009
Telecom Testing
Telecom Testing
By Rohit Aggarwal
Testing in telecom world is as vast a subject as the domain itself. This blog talks about the readiness to become a telecom tester. The intent is to address the apprehensions and misconceptions; the actual tools and methodologies involved form the next level of discussion.
Kick-start
Do not jump to the System Under Test (SUT). Start from the bigger picture.
For instance, understand the technological domain/network, then the network nodes, then the SUT as a black box.
W5H of the System Under Test
There is a lot of food for thought. It is important to answer a few questions to be able to prepare the use cases and test details.
i. What does it do: functionality
ii. Where is it placed: network positioning
iii. Why is it needed: network architecture, business drivers
iv. Who will use it: end user – could be human being or another network node
v. When is it used: time, service, peak usage etc.
vi. How does it work: protocol, language, interfaces
Knowledge of deployment zone is a value-add. Test criteria needs to consider regional policies, infrastructure and usage patterns.
Documentation
A lot of information about the SUT is available through
? Technical specifications sheet
? Release bulletin
? User Manual
? Requirement Specifications
and other technical documents.
Types of Testing
There are multiple behavioral elements of the SUT that need to be tested.
? Functional
? Compliance
? Performance
? Load
? Soak
One of the key facets is that most of the telecom equipment is real-time.
Test Environment
Test tools can be
? Purchased: cost-driven
? Produced: time-driven
? Procured: contract-driven
Investment
? Ramp up
? Time: large amount of time needed to understand the technical specifications
? Cost: almost entire knowledge base freely available on web
? Test bed
? Time: to code test stubs
? Cost: to buy test stubs e.g., OS, compiler, network software, equipment
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
By Rohit Aggarwal
Testing in telecom world is as vast a subject as the domain itself. This blog talks about the readiness to become a telecom tester. The intent is to address the apprehensions and misconceptions; the actual tools and methodologies involved form the next level of discussion.
Kick-start
Do not jump to the System Under Test (SUT). Start from the bigger picture.
For instance, understand the technological domain/network, then the network nodes, then the SUT as a black box.
W5H of the System Under Test
There is a lot of food for thought. It is important to answer a few questions to be able to prepare the use cases and test details.
i. What does it do: functionality
ii. Where is it placed: network positioning
iii. Why is it needed: network architecture, business drivers
iv. Who will use it: end user – could be human being or another network node
v. When is it used: time, service, peak usage etc.
vi. How does it work: protocol, language, interfaces
Knowledge of deployment zone is a value-add. Test criteria needs to consider regional policies, infrastructure and usage patterns.
Documentation
A lot of information about the SUT is available through
? Technical specifications sheet
? Release bulletin
? User Manual
? Requirement Specifications
and other technical documents.
Types of Testing
There are multiple behavioral elements of the SUT that need to be tested.
? Functional
? Compliance
? Performance
? Load
? Soak
One of the key facets is that most of the telecom equipment is real-time.
Test Environment
Test tools can be
? Purchased: cost-driven
? Produced: time-driven
? Procured: contract-driven
Investment
? Ramp up
? Time: large amount of time needed to understand the technical specifications
? Cost: almost entire knowledge base freely available on web
? Test bed
? Time: to code test stubs
? Cost: to buy test stubs e.g., OS, compiler, network software, equipment
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
A Beginner’s Blog to Performance Testing
A Beginner’s Blog to Performance Testing
Blog Home »
*
Calender
May 2009 M T W T F S S
« Apr
1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
*
Recent Posts
o Updates about QTP 10 (I)
o Agent Controller Issue on Starting RAServer Process
o Oracle Tunning
o Bridging the Gap between Open Source & Commercial Tools
o Necessity- the Mother of all Invention (Part II)
*
Archives
o May 2009
o April 2009
o March 2009
o February 2009
o January 2009
o October 2008
o September 2008
o August 2008
o July 2008
*
Tags
Agile Mode CRM | Database Document Object Model | Functional Automation Functional Testing | General General Concepts human resource Human Resources | Open Source Tools Oracle Performance Testing | QTP SRS Telecom Testing
Search Blog
*
Categories
o Catch The Latest
o CRM |
o Functional Automation
o Functional Testing |
o General
o General Concepts
o Human Resources |
o Open Source tools
o Open Source tools
o Other Commercial Tools
o Performance Testing |
o Quick Test Professional
o Rational Functional Tester
o Security Testing
o Telecom Testing
o Testing SOA
o Uncategorized
*
Recent Comments
o Abhay on Sample code to click on dynamic link using Browser DOM
o parul wahi on Testing Ajax Application using QTP
o Pankaj Goel on Testing Ajax Application using QTP
o Pankaj Goel on Oracle Tunning
o Pankaj Goel on Bridging the Gap between Open Source & Commercial Tools
*
Blogger
o Roshi Malhotra
o Kuldeep Singh
o Vaibhav Agarwal
o Rajat Singhal
o Avinash K. Tiwari
o Ravinder Singroha
o Vivek Goyal
o Sudha Sharma
o Betsy Joy
o Shalini Rawal
A Beginner’s Blog to Performance Testing
July 29th, 2008 admin Posted in General Concepts |
By Happy Himanshu Gupta
Class 12th Board results were out and I ran to my PC to check the result. The anxiety level was rising every moment as it was taking time for the result page to open. Why is this page taking so long to open…?? Have I scored less…or perhaps I have failed in Chemistry..?? Oh god……!!!! What is going to happen… :( ?? Finally after 7 minutes and a few seconds, I rested in peace when the internet page opened and highlighted PASS on the screen. I just kicked my PC for taking the life out of me in those 7 minutes.
It’s just been a few days that I have stopped cursing my poor machine for those worst 7 minutes of my life when I came across a term called “Performance Testing”. I felt like sharing the definition of this term with you people and got up to writing this starting blog. :)
Performance testing is an emerging science in the field of Software testing. When we talk about effective development of an application that makes life easy, we cannot neglect its high performance as one of the major factors contributing to its quality. Performance testing is done to test a specific behavior of the application. But is there any specific criterion to define performance?
To define the concepts of performance of any system software or any general application (web/system), we can define a phrase “meeting of requirements with the timeliness” of the application. A well running application will always meet its requirements under the benchmark indicators. We map these benchmarks to the actual performance counters, which help us to judge, how the application is performing under the current environment.
These performance counters can broadly be categorized into two major dimensions, namely, Responsiveness and Scalability.
Response time of an application is the time required to process any instruction and return back the result. It is the waiting time, the measure of which is directly proportional to the number of concurrent users working on the application.
Throughput of the system is the number of events which an application can process within some interval of time. More the throughput better is the performance of the application.
Scalability of an application can be defined by its ability to meet the throughput and the response time objectives, even as the load on the application continue to increase with the increasing functionaries. Better performance is achieved by high scalability of the application.
Though Performance testing is done in conjunction with stress testing, but performance testing is not only stress testing. It covers the other aspects such as load testing and endurance testing along with the stress testing.
There are a number of tools, both commercial and open-source, to facilitate performance testing of any application. Commercial tools like Load Runner (LR) and Rational Performance Tester (RPT) are well equipped to support a number of different protocols for performance testing. Open-source tools such as OpenSTA, JMeter, Grinder, Webload etc. have made it easy for the small scale IT industries to test the performance of their applications without spending a substantial sum on gaining the licenses of their commercial counterparts.
Performance testing allows the user to identify the bottleneck in the application, which is the cause of the poor performance. The relational graphs and the statistical values of the performance counters help in analyzing the behavior of the application with the increasing load (number of users).
Well friends, the heavy rush on the Result website was the actual reason for the delay in the result that night and not my poor PC. I believe such websites should go for the performance testing of their applications before giving nightmares to the innocent children…. :)
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
AddThis Social Bookmark Button
2 Responses to “A Beginner’s Blog to Performance Testing”
1.
Aaisha Ghosh Says:
July 30th, 2008 at 10:47 pm
:-) A Nice Read Himanshu. I am a functional tester and have been curious to Know how to get started in Performance Testing. Since you have already taken this first step, can u guide me in what all to read.
Is there some good training institute where i can get performance testing training
2.
Happy Himanshu Gupta Says:
August 4th, 2008 at 3:22 am
Thanks for your comments Aaisha. I will keep updating the blog adding more to this particular domain of testing , to help all the learners gain the primary knowledge of Performance Testing.
“QACampus”, is a one stop testing portal, which is maintained by the Learning and Training Devision of our organization. Just check out the ‘Contact Us’ section on this website, to reach out to us for any query. I believe QACampus is the best place to learn any aspect of testing.
Leave a Reply
Name (required)
Mail (will not be published) (required)
Website
(Required)
Type the two words:Type what you hear:Incorrect. Try again.
Get a new challenge
Get an audio challengeGet a visual challenge
Help
« Telecom Testing
Introduction To HR Payroll »
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
Blog Home »
*
Calender
May 2009 M T W T F S S
« Apr
1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
*
Recent Posts
o Updates about QTP 10 (I)
o Agent Controller Issue on Starting RAServer Process
o Oracle Tunning
o Bridging the Gap between Open Source & Commercial Tools
o Necessity- the Mother of all Invention (Part II)
*
Archives
o May 2009
o April 2009
o March 2009
o February 2009
o January 2009
o October 2008
o September 2008
o August 2008
o July 2008
*
Tags
Agile Mode CRM | Database Document Object Model | Functional Automation Functional Testing | General General Concepts human resource Human Resources | Open Source Tools Oracle Performance Testing | QTP SRS Telecom Testing
Search Blog
*
Categories
o Catch The Latest
o CRM |
o Functional Automation
o Functional Testing |
o General
o General Concepts
o Human Resources |
o Open Source tools
o Open Source tools
o Other Commercial Tools
o Performance Testing |
o Quick Test Professional
o Rational Functional Tester
o Security Testing
o Telecom Testing
o Testing SOA
o Uncategorized
*
Recent Comments
o Abhay on Sample code to click on dynamic link using Browser DOM
o parul wahi on Testing Ajax Application using QTP
o Pankaj Goel on Testing Ajax Application using QTP
o Pankaj Goel on Oracle Tunning
o Pankaj Goel on Bridging the Gap between Open Source & Commercial Tools
*
Blogger
o Roshi Malhotra
o Kuldeep Singh
o Vaibhav Agarwal
o Rajat Singhal
o Avinash K. Tiwari
o Ravinder Singroha
o Vivek Goyal
o Sudha Sharma
o Betsy Joy
o Shalini Rawal
A Beginner’s Blog to Performance Testing
July 29th, 2008 admin Posted in General Concepts |
By Happy Himanshu Gupta
Class 12th Board results were out and I ran to my PC to check the result. The anxiety level was rising every moment as it was taking time for the result page to open. Why is this page taking so long to open…?? Have I scored less…or perhaps I have failed in Chemistry..?? Oh god……!!!! What is going to happen… :( ?? Finally after 7 minutes and a few seconds, I rested in peace when the internet page opened and highlighted PASS on the screen. I just kicked my PC for taking the life out of me in those 7 minutes.
It’s just been a few days that I have stopped cursing my poor machine for those worst 7 minutes of my life when I came across a term called “Performance Testing”. I felt like sharing the definition of this term with you people and got up to writing this starting blog. :)
Performance testing is an emerging science in the field of Software testing. When we talk about effective development of an application that makes life easy, we cannot neglect its high performance as one of the major factors contributing to its quality. Performance testing is done to test a specific behavior of the application. But is there any specific criterion to define performance?
To define the concepts of performance of any system software or any general application (web/system), we can define a phrase “meeting of requirements with the timeliness” of the application. A well running application will always meet its requirements under the benchmark indicators. We map these benchmarks to the actual performance counters, which help us to judge, how the application is performing under the current environment.
These performance counters can broadly be categorized into two major dimensions, namely, Responsiveness and Scalability.
Response time of an application is the time required to process any instruction and return back the result. It is the waiting time, the measure of which is directly proportional to the number of concurrent users working on the application.
Throughput of the system is the number of events which an application can process within some interval of time. More the throughput better is the performance of the application.
Scalability of an application can be defined by its ability to meet the throughput and the response time objectives, even as the load on the application continue to increase with the increasing functionaries. Better performance is achieved by high scalability of the application.
Though Performance testing is done in conjunction with stress testing, but performance testing is not only stress testing. It covers the other aspects such as load testing and endurance testing along with the stress testing.
There are a number of tools, both commercial and open-source, to facilitate performance testing of any application. Commercial tools like Load Runner (LR) and Rational Performance Tester (RPT) are well equipped to support a number of different protocols for performance testing. Open-source tools such as OpenSTA, JMeter, Grinder, Webload etc. have made it easy for the small scale IT industries to test the performance of their applications without spending a substantial sum on gaining the licenses of their commercial counterparts.
Performance testing allows the user to identify the bottleneck in the application, which is the cause of the poor performance. The relational graphs and the statistical values of the performance counters help in analyzing the behavior of the application with the increasing load (number of users).
Well friends, the heavy rush on the Result website was the actual reason for the delay in the result that night and not my poor PC. I believe such websites should go for the performance testing of their applications before giving nightmares to the innocent children…. :)
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
AddThis Social Bookmark Button
2 Responses to “A Beginner’s Blog to Performance Testing”
1.
Aaisha Ghosh Says:
July 30th, 2008 at 10:47 pm
:-) A Nice Read Himanshu. I am a functional tester and have been curious to Know how to get started in Performance Testing. Since you have already taken this first step, can u guide me in what all to read.
Is there some good training institute where i can get performance testing training
2.
Happy Himanshu Gupta Says:
August 4th, 2008 at 3:22 am
Thanks for your comments Aaisha. I will keep updating the blog adding more to this particular domain of testing , to help all the learners gain the primary knowledge of Performance Testing.
“QACampus”, is a one stop testing portal, which is maintained by the Learning and Training Devision of our organization. Just check out the ‘Contact Us’ section on this website, to reach out to us for any query. I believe QACampus is the best place to learn any aspect of testing.
Leave a Reply
Name (required)
Mail (will not be published) (required)
Website
(Required)
Type the two words:Type what you hear:Incorrect. Try again.
Get a new challenge
Get an audio challengeGet a visual challenge
Help
« Telecom Testing
Introduction To HR Payroll »
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
Introduction To HR Payroll
By Anurag Vasisht
Introduction
Payroll is one business area that is of relevance to all of us. We all work to get paid (or most us, anyway). In good old days, this payment used to be a straight affair of a fixed salary OR a simple multiplication of number of hours with hourly rate. Not any more. Nowadays, it’s a much more complicated process with concepts like deductions, contributions, exemptions, taxation laws, union contracts, commissions, loans, bonus payments and other special payments/deductions. HR Payroll also provides input to downstream systems like Finance Accounting, General Ledger etc.
For the purpose of understanding the nuts and bolts of HR Payroll, let us define employees under the following broad categories. This distinction is required because the Payroll processing is vastly different for these categories. Most employers, big or small, follow this segregation at the topmost level, drilling down to different levels of complexity based on size and diversification of their businesses.
1. Non-Exempt
These employees are required to accurately record the time that they spend on work. If different types of work have different payment rates, then they are expected to record time against different “attendance/work codes”. If time is not recorded for work done, then no payments are made for that work.
Such employees are setup with an expected daily/weekly hours and basic rate of pay instead of a fixed/basic salary. If these employees work more than their schedule, then they are paid overtime at a normal or premium rate as defined.
In some cases, such employees are contracted through Labor Unions and are paid as per the terms and conditions as defined in the respective contracts.
2. Exempt
These employees are exempt from recording their time on work. Such employees are setup with a schedule (such as Mon-Fri 9-6) and are expected to report time only if some exception happens from their normal schedule (such as vacation or jury call or military duty). Unless they report an exception it is understood that they followed their schedule. Though employers do set up in/out devices for monitoring purpose and deviations are questioned, but these typically do not impact the payments unless there is a drastic variation.
Typically, management employees fall under this category while non-management employees are under Non-Exempt category.
2. Stages of Payroll processing
1. Employee setup
This is the static information which is typically set up for an employee at Hire time and updated typically at the start of a financial year. This is expected to remain the same till there is change in status of the employee, caused by events such as promotion, termination, demotion, change of job profile or location etc. Setup information includes data such as type of employee, job profile, work location, work schedule, leave entitlements, payroll cycle (weekly, semi-monthly, monthly etc), basic pay (or rate of pay), compensation and benefits, medical and insurance plans etc. This setup pretty much defines the way actual processing happens at the end of every payroll cycle.
2. Attendance/Absence Records
Non exempt employees record each hour and minute of work against relevant attendance code. This time is compared against the work schedule and determined if any premium is to be paid against overtime, holiday worked etc.
In case of absence in scheduled work hours, time is coded against the relevant absence codes. This is applicable for both exempt and non-exempt employees. Absences are compared against the leave entitlements, and determined if they need to be paid out or any deductions need to be made.
3. Calculation of Gross Pay
It is typically the summation of all earnings. For non-exempt employees, the figure arrived from number of hours X hourly rate can start as the basis while for exempt employees, the basic salary can for the basis. In this figure, various garnishments are added to arrive at the Gross Pay. These include overtime/holiday worked premiums, commissions, bonus payments, arrears from previous salaries, misc benefits etc.
4. Calculation of Net Pay
This calculated by subtracting the various deductions and taxes from the Gross Pay. Deductions may include loan payments, union dues, overpayments of previous salaries, contributions to misc health/benefit/insurance plans. Taxes are generally applied after deductions and include federal, state and local taxes. Net Pay is what an employee gets in his account.
3. Key Considerations in Testing
1. Setup & Locale: Payroll processing is different for each country, and sometimes there are major differences with in states in a country. Even though generic rules are good to have an overview, a thorough understanding of the local (financial, labor and taxation) laws is essential. Similarly, HR policies of a company that govern all the Payroll processing are important to learn and comprehend before jumping headlong into IT solution that implements those policies. Finally, knowledge of IT solution (implementation) is recommended as each vendor differs vastly from the other, and even in case of black box system testing, it does no harm to know the vital aspects.
2. Movements: Any kind of movement brings complexity to the system. Whether it was a Hire, Rehire, Termination, Transfer from one location to another, Promotion, Demotion: all of these visibly impact the payroll processing. Much of the complexity can be removed if a company prohibits movements in the mid of a pay period. Then, there is a clear demarcation, and the process can be easily developed and tested to take notice of such a movement. However, if there is no such restriction, then it is a nightmare…requiring much more analysis in understanding, implementing and testing the solution.
3. “Worked/Earned” vs. “Paid”: This concept is critical in case of reports which run out of Payroll. Consider this example: An employee works for the period 12/16/07 to 12/31/07. His Payroll processing happens on 1/3/08 and gets paid on 1/5/08. Now, assuming there is monthly report which displays employee wages. In this case, should the amount for the work done between 12/16/07 to 12/31/07 appear in Dec 07 report or Jan 08 report? There is no default answer to this question, and depends from case to case – determined by the business that uses the report. So, this question must definitely be asked for any Payroll report testing.
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
By Anurag Vasisht
Introduction
Payroll is one business area that is of relevance to all of us. We all work to get paid (or most us, anyway). In good old days, this payment used to be a straight affair of a fixed salary OR a simple multiplication of number of hours with hourly rate. Not any more. Nowadays, it’s a much more complicated process with concepts like deductions, contributions, exemptions, taxation laws, union contracts, commissions, loans, bonus payments and other special payments/deductions. HR Payroll also provides input to downstream systems like Finance Accounting, General Ledger etc.
For the purpose of understanding the nuts and bolts of HR Payroll, let us define employees under the following broad categories. This distinction is required because the Payroll processing is vastly different for these categories. Most employers, big or small, follow this segregation at the topmost level, drilling down to different levels of complexity based on size and diversification of their businesses.
1. Non-Exempt
These employees are required to accurately record the time that they spend on work. If different types of work have different payment rates, then they are expected to record time against different “attendance/work codes”. If time is not recorded for work done, then no payments are made for that work.
Such employees are setup with an expected daily/weekly hours and basic rate of pay instead of a fixed/basic salary. If these employees work more than their schedule, then they are paid overtime at a normal or premium rate as defined.
In some cases, such employees are contracted through Labor Unions and are paid as per the terms and conditions as defined in the respective contracts.
2. Exempt
These employees are exempt from recording their time on work. Such employees are setup with a schedule (such as Mon-Fri 9-6) and are expected to report time only if some exception happens from their normal schedule (such as vacation or jury call or military duty). Unless they report an exception it is understood that they followed their schedule. Though employers do set up in/out devices for monitoring purpose and deviations are questioned, but these typically do not impact the payments unless there is a drastic variation.
Typically, management employees fall under this category while non-management employees are under Non-Exempt category.
2. Stages of Payroll processing
1. Employee setup
This is the static information which is typically set up for an employee at Hire time and updated typically at the start of a financial year. This is expected to remain the same till there is change in status of the employee, caused by events such as promotion, termination, demotion, change of job profile or location etc. Setup information includes data such as type of employee, job profile, work location, work schedule, leave entitlements, payroll cycle (weekly, semi-monthly, monthly etc), basic pay (or rate of pay), compensation and benefits, medical and insurance plans etc. This setup pretty much defines the way actual processing happens at the end of every payroll cycle.
2. Attendance/Absence Records
Non exempt employees record each hour and minute of work against relevant attendance code. This time is compared against the work schedule and determined if any premium is to be paid against overtime, holiday worked etc.
In case of absence in scheduled work hours, time is coded against the relevant absence codes. This is applicable for both exempt and non-exempt employees. Absences are compared against the leave entitlements, and determined if they need to be paid out or any deductions need to be made.
3. Calculation of Gross Pay
It is typically the summation of all earnings. For non-exempt employees, the figure arrived from number of hours X hourly rate can start as the basis while for exempt employees, the basic salary can for the basis. In this figure, various garnishments are added to arrive at the Gross Pay. These include overtime/holiday worked premiums, commissions, bonus payments, arrears from previous salaries, misc benefits etc.
4. Calculation of Net Pay
This calculated by subtracting the various deductions and taxes from the Gross Pay. Deductions may include loan payments, union dues, overpayments of previous salaries, contributions to misc health/benefit/insurance plans. Taxes are generally applied after deductions and include federal, state and local taxes. Net Pay is what an employee gets in his account.
3. Key Considerations in Testing
1. Setup & Locale: Payroll processing is different for each country, and sometimes there are major differences with in states in a country. Even though generic rules are good to have an overview, a thorough understanding of the local (financial, labor and taxation) laws is essential. Similarly, HR policies of a company that govern all the Payroll processing are important to learn and comprehend before jumping headlong into IT solution that implements those policies. Finally, knowledge of IT solution (implementation) is recommended as each vendor differs vastly from the other, and even in case of black box system testing, it does no harm to know the vital aspects.
2. Movements: Any kind of movement brings complexity to the system. Whether it was a Hire, Rehire, Termination, Transfer from one location to another, Promotion, Demotion: all of these visibly impact the payroll processing. Much of the complexity can be removed if a company prohibits movements in the mid of a pay period. Then, there is a clear demarcation, and the process can be easily developed and tested to take notice of such a movement. However, if there is no such restriction, then it is a nightmare…requiring much more analysis in understanding, implementing and testing the solution.
3. “Worked/Earned” vs. “Paid”: This concept is critical in case of reports which run out of Payroll. Consider this example: An employee works for the period 12/16/07 to 12/31/07. His Payroll processing happens on 1/3/08 and gets paid on 1/5/08. Now, assuming there is monthly report which displays employee wages. In this case, should the amount for the work done between 12/16/07 to 12/31/07 appear in Dec 07 report or Jan 08 report? There is no default answer to this question, and depends from case to case – determined by the business that uses the report. So, this question must definitely be asked for any Payroll report testing.
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
Monday, May 18, 2009
IBM Rational Functional Testing
IBM Rational Functional Testing
By Vaibhav Agarwal
Now a days most of us (in IT industry) know/have heard about Automated testing tools.
Rational Functional Tester (RFT), as the name says, is an automated functional testing tool from Rational. This tool tests your application automatically without human intervention.
IBM Rational Functional Tester is an object-oriented automated testing tool that lets you test a variety of applications. You can quickly generate scripts by recording tests against an application, and you can test any object in the application, including the object’s properties and data. Rational Functional Tester offers you a choice of scripting language and development environment — Java in the Eclipse framework or Microsoft Visual Basic .NET in the Microsoft Visual Studio .NET Development Environment. That means that regardless of the language or platform your development staff has chosen, you should be able to integrate with them and leverage some of their expertise as you develop your automated tests.
Rational Functional Tester offers these powerful capabilities
• Play back scripts against an updated application
• Update recognition properties for an object
• Merge multiple test object maps
• Display associated scripts
• Use pattern-based object recognition
• Integrate with UCM
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
By Vaibhav Agarwal
Now a days most of us (in IT industry) know/have heard about Automated testing tools.
Rational Functional Tester (RFT), as the name says, is an automated functional testing tool from Rational. This tool tests your application automatically without human intervention.
IBM Rational Functional Tester is an object-oriented automated testing tool that lets you test a variety of applications. You can quickly generate scripts by recording tests against an application, and you can test any object in the application, including the object’s properties and data. Rational Functional Tester offers you a choice of scripting language and development environment — Java in the Eclipse framework or Microsoft Visual Basic .NET in the Microsoft Visual Studio .NET Development Environment. That means that regardless of the language or platform your development staff has chosen, you should be able to integrate with them and leverage some of their expertise as you develop your automated tests.
Rational Functional Tester offers these powerful capabilities
• Play back scripts against an updated application
• Update recognition properties for an object
• Merge multiple test object maps
• Display associated scripts
• Use pattern-based object recognition
• Integrate with UCM
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
Working with Excel objects in QTP
Working with Excel objects in QTP
We create framework for automating the application. For this we need the independent structure for reporting and data. Excel plays a very important role in this approach.
QTP has its own test result displaying mechanism in the predefined format. Once the test is run, the result sheet is generated which gives you the insight of the script – stating the point of failures, warnings and passes.
We create customized checkpoint in the script and it is possible to customize the result file also depending upon the checkpoint created will be passed or failed.
In most of the cases we want to create summarized or detailed report of the entire test in excels. The reason to create customized report is that one is able to keep the file in central location and to create the report in our own format.
In this article we are going to learn the interaction of Excel with VBScript.
The whole mechanism goes in the following steps:
1. Understanding the hierarchy of Excel Application.
2. Creating the Excel Object
3. Opening an existing workbook or creating the new one
4. Setting the objects for various sheets in workbook.
5. Writing and fetching the data values in the cells.
6. Saving and closing the workbook
7. Closing the application and releasing the memory
We will go through each of the above stated steps with a suitable example to understand the approach properly.
Understanding the hierarchy of Excel Application
We will not go into the details of the complete hierarchy of the Excel application but to the extend what is required.
Excel Application
Workbooks
Sheets
Cells
Creating the Excel Object
The first step towards the process of reporting via excel is to create object of Excel. Reporting in Excel can either be done in backend, without making the application visible or u can make it appear to user once the process of writing or fetching the data is going. In either way creating of the Excel Application object is required.
It goes as:
Dim xl
Set xl = CreateObject(“Excel.Application”)
Opening an existing workbook or creating the new one
Once the excel object has been created, it means that excel application has been invoked but is not visible. So either one can perform the operations like that or make the application visible and then perform the operations.
To make the application visible:
xl.visible = true
To open a new Workbook:
xl.workbooks.Add
To open an existing Workbook:
xl.workbooks.Open(“File Name with complete path”)
Setting and accessing the objects of sheets in workbook.
Once the workbook has been opened, either existing or new one, we need to write some data in various cells in various sheets of that workbook.
By default there are 3 sheets in a workbook and various operations can be performed on. So one need create the object to reference these sheets as it becomes easy to access them and you don’t have to mention the complete hierarchy over and over again.
Say one has to create a reference for sheet with index i, which starts from 1
Set sht1 = xl.activeworkbook.sheets(i)
One can add or delete n number of sheets from the activeworkbook
To add a sheet in workbook –
xl.activeworkbook.sheets.add
To delete a particular sheet where i represent the index which starts from 1 –
xl.activeworkbook.sheets(i).delete
To change the name of the sheets –
xl.activeworkbook.sheeets(i).name = “Name of your choice”
To count the total number of sheets in the workbook
Cnt = xl.activeworkbook.sheets.count
Writing and fetching the data values in the cells
To write the data in Excel sheet, one should know the cell address in which the data has to be written. Same thing goes for accessing the data from the cells
To write the data in sheet2 cell address as D8, we write the following command. Cell address here is represented by row number followed by column number –
xl.activeworkbook.sheets(2).cells(8,4) = “hello”
To fetch the data from sheet3 cell address A7 –
Val = xl.activeworkbook.sheets(3).cells(7,1)
If one has already created the object of the particular sheet, you don’t have to write the complete hierarchy but simply –
Object.cells(row,col) = value
Saving and closing the workbook
Once the work completed you can save the newly created workbook to a specified location or save the changes made to already existing opened workbook.
To save as in case of new workbook
xl.activeworkbook.saveas “path_with_file_name.xls”
To save in case of existing workbook
xl.activeworkbook.save
To close the workbook
xl.activeworkbook.close
Closing the application and releasing the memory
To close the application
xl.quit
To release the memory of all the objects
Set xl = nothing
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
We create framework for automating the application. For this we need the independent structure for reporting and data. Excel plays a very important role in this approach.
QTP has its own test result displaying mechanism in the predefined format. Once the test is run, the result sheet is generated which gives you the insight of the script – stating the point of failures, warnings and passes.
We create customized checkpoint in the script and it is possible to customize the result file also depending upon the checkpoint created will be passed or failed.
In most of the cases we want to create summarized or detailed report of the entire test in excels. The reason to create customized report is that one is able to keep the file in central location and to create the report in our own format.
In this article we are going to learn the interaction of Excel with VBScript.
The whole mechanism goes in the following steps:
1. Understanding the hierarchy of Excel Application.
2. Creating the Excel Object
3. Opening an existing workbook or creating the new one
4. Setting the objects for various sheets in workbook.
5. Writing and fetching the data values in the cells.
6. Saving and closing the workbook
7. Closing the application and releasing the memory
We will go through each of the above stated steps with a suitable example to understand the approach properly.
Understanding the hierarchy of Excel Application
We will not go into the details of the complete hierarchy of the Excel application but to the extend what is required.
Excel Application
Workbooks
Sheets
Cells
Creating the Excel Object
The first step towards the process of reporting via excel is to create object of Excel. Reporting in Excel can either be done in backend, without making the application visible or u can make it appear to user once the process of writing or fetching the data is going. In either way creating of the Excel Application object is required.
It goes as:
Dim xl
Set xl = CreateObject(“Excel.Application”)
Opening an existing workbook or creating the new one
Once the excel object has been created, it means that excel application has been invoked but is not visible. So either one can perform the operations like that or make the application visible and then perform the operations.
To make the application visible:
xl.visible = true
To open a new Workbook:
xl.workbooks.Add
To open an existing Workbook:
xl.workbooks.Open(“File Name with complete path”)
Setting and accessing the objects of sheets in workbook.
Once the workbook has been opened, either existing or new one, we need to write some data in various cells in various sheets of that workbook.
By default there are 3 sheets in a workbook and various operations can be performed on. So one need create the object to reference these sheets as it becomes easy to access them and you don’t have to mention the complete hierarchy over and over again.
Say one has to create a reference for sheet with index i, which starts from 1
Set sht1 = xl.activeworkbook.sheets(i)
One can add or delete n number of sheets from the activeworkbook
To add a sheet in workbook –
xl.activeworkbook.sheets.add
To delete a particular sheet where i represent the index which starts from 1 –
xl.activeworkbook.sheets(i).delete
To change the name of the sheets –
xl.activeworkbook.sheeets(i).name = “Name of your choice”
To count the total number of sheets in the workbook
Cnt = xl.activeworkbook.sheets.count
Writing and fetching the data values in the cells
To write the data in Excel sheet, one should know the cell address in which the data has to be written. Same thing goes for accessing the data from the cells
To write the data in sheet2 cell address as D8, we write the following command. Cell address here is represented by row number followed by column number –
xl.activeworkbook.sheets(2).cells(8,4) = “hello”
To fetch the data from sheet3 cell address A7 –
Val = xl.activeworkbook.sheets(3).cells(7,1)
If one has already created the object of the particular sheet, you don’t have to write the complete hierarchy but simply –
Object.cells(row,col) = value
Saving and closing the workbook
Once the work completed you can save the newly created workbook to a specified location or save the changes made to already existing opened workbook.
To save as in case of new workbook
xl.activeworkbook.saveas “path_with_file_name.xls”
To save in case of existing workbook
xl.activeworkbook.save
To close the workbook
xl.activeworkbook.close
Closing the application and releasing the memory
To close the application
xl.quit
To release the memory of all the objects
Set xl = nothing
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
Rational Functional Tester- Features and benefits
Rational Functional Tester- Features and benefits
1. Ensure playback resilient to application changes with ScriptAssure technology -
Frequent changes to an application’s user interface can hamper test script execution. IBM Rational Functional Tester introduces an advanced ScriptAssure™ technology to accommodate these changes and avoid increases in maintenance overhead. ScriptAssure uses fuzzy matching algorithms to locate objects during test execution, even if the objects have changed since test creation.
2. Increase script re-use with wizard for data driven test creation –
Data driven tests are functional tests that perform the same series of test actions, but with varying data. IBM Rational Functional Tester can automatically detect data entered during test recording and prepare the test for data-driven testing. Using a spreadsheet-like data editor, you can then create customized data sets to be used by the test during playback. In this way, you can achieve test script re-use without time consuming manual coding.
3. Streamline automation with keyword testing –
Rational Functional Tester provides ability to define and automate keywords which can be reused in both functional and manual tests. This promotes script reuse and enables manual testers to easily and selectively leverage the power of automation within manual test cycles.
4. Proxy SDK –
This feature allows testers to define support for custom controls.
5. Choice of test editing language - Java or Visual Basic .NET –
Test script customization is mandatory in order to perform anything but the most basic tests. IBM Rational Functional Tester gives you a choice of powerful, mainstream scripting languages to make this possible. Choose between either Java or Visual Basic .NET - both options can be used with all the supported user interface technologies. By working with Functional Tester, testers quickly learn to work with basic language constructs and acquire programming skills that facilitate more productive communication with developers.
6. Validate dynamic data with dynamic data validation wizard –
Validating dynamic data, such as time stamps or order confirmation numbers can be tedious time consuming task, involving complex manual coding. IBM Rational Functional Tester includes wizard driven support for regular expression dynamic data validation. Users can effortlessly validate dynamic data against template patterns without having to write complex code.
7. Manual Test Automation support –
For teams not yet prepared to automate all of their testing efforts, IBM Rational Manual Tester is included in the Rational Functional Tester product box. Rational Manual Tester brings control and organization to manual testing efforts, introducing automated data entry and data validation to manual.
8. Test script version control for parallel development –
Typically, more than one version of an application is deployed within an organization, and testers must therefore maintain groups of tests for each version. Without the help of automated version control, this can be extremely difficult. IBM Rational Functional Tester is designed to support automated version control, which not only provides a mechanism to maintain multiple test sets, but also enables parallel development and supports geographically dispersed teams, To help teams take advantage of this support, a full version of IBM Rational ClearCase LT, an entry-level version control tool designed for small project workgroups, is included in the product box. Rational Functional Tester users also have the option of upgrading to the standard version of IBM Rational ClearCase.
9. Native Java and Visual Basic .NET editor and debugger for advanced testers –
Test script editing is important, but it can be difficult without a good editor and debugger. IBM Rational Functional Tester delivers industrial-strength options to address this concern. Testers using Java can work in the Eclipse Java editor and those using Visual Basic .NET can work in Visual Studio .NET. Both integrated development environments offer a host of options to simplify test enhancement, including a helpful code-complete feature that suggests code to accelerate editing. GUI developers will find this feature particularly useful, as they can access it within the IDE they use to build the user interface.
10.Linux test editing and test execution support –
For cross-platform Java applications, IBM Rational Functional Tester offers scripting to create, edit, and execute tests on the Linux platform - including everything except a test recorder. It also supports the Windows platform for all recording, editing, and execution capabilities.
11.Add-on support available for testing 3270/5250 terminal-based applications –
Teams responsible for testing mixed workload environments - environments comprised of both Java/Web/Visual Studio .NET-based applications and mainframe-based applications - can purchase the IBM Rational Functional Tester Extension for Terminal-based Applications. This extension enables automation and testing for 3270 and 5250 terminal-based applications, including automated data entry and response verification, using the testing tool and scripting language the tester favors for Windows and Linux-based applications.
12.Extended automated functional and regression testing for Siebel® and SAP® applications –
IBM Rational Functional Tester Extension for Siebel Test Automation interfaces to provide robust automation support for both Siebel 7.7 and 7.8. IBM Rational Functional Tester Extension Automated test creation, execution and analysis of SAP GUI applications.
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
1. Ensure playback resilient to application changes with ScriptAssure technology -
Frequent changes to an application’s user interface can hamper test script execution. IBM Rational Functional Tester introduces an advanced ScriptAssure™ technology to accommodate these changes and avoid increases in maintenance overhead. ScriptAssure uses fuzzy matching algorithms to locate objects during test execution, even if the objects have changed since test creation.
2. Increase script re-use with wizard for data driven test creation –
Data driven tests are functional tests that perform the same series of test actions, but with varying data. IBM Rational Functional Tester can automatically detect data entered during test recording and prepare the test for data-driven testing. Using a spreadsheet-like data editor, you can then create customized data sets to be used by the test during playback. In this way, you can achieve test script re-use without time consuming manual coding.
3. Streamline automation with keyword testing –
Rational Functional Tester provides ability to define and automate keywords which can be reused in both functional and manual tests. This promotes script reuse and enables manual testers to easily and selectively leverage the power of automation within manual test cycles.
4. Proxy SDK –
This feature allows testers to define support for custom controls.
5. Choice of test editing language - Java or Visual Basic .NET –
Test script customization is mandatory in order to perform anything but the most basic tests. IBM Rational Functional Tester gives you a choice of powerful, mainstream scripting languages to make this possible. Choose between either Java or Visual Basic .NET - both options can be used with all the supported user interface technologies. By working with Functional Tester, testers quickly learn to work with basic language constructs and acquire programming skills that facilitate more productive communication with developers.
6. Validate dynamic data with dynamic data validation wizard –
Validating dynamic data, such as time stamps or order confirmation numbers can be tedious time consuming task, involving complex manual coding. IBM Rational Functional Tester includes wizard driven support for regular expression dynamic data validation. Users can effortlessly validate dynamic data against template patterns without having to write complex code.
7. Manual Test Automation support –
For teams not yet prepared to automate all of their testing efforts, IBM Rational Manual Tester is included in the Rational Functional Tester product box. Rational Manual Tester brings control and organization to manual testing efforts, introducing automated data entry and data validation to manual.
8. Test script version control for parallel development –
Typically, more than one version of an application is deployed within an organization, and testers must therefore maintain groups of tests for each version. Without the help of automated version control, this can be extremely difficult. IBM Rational Functional Tester is designed to support automated version control, which not only provides a mechanism to maintain multiple test sets, but also enables parallel development and supports geographically dispersed teams, To help teams take advantage of this support, a full version of IBM Rational ClearCase LT, an entry-level version control tool designed for small project workgroups, is included in the product box. Rational Functional Tester users also have the option of upgrading to the standard version of IBM Rational ClearCase.
9. Native Java and Visual Basic .NET editor and debugger for advanced testers –
Test script editing is important, but it can be difficult without a good editor and debugger. IBM Rational Functional Tester delivers industrial-strength options to address this concern. Testers using Java can work in the Eclipse Java editor and those using Visual Basic .NET can work in Visual Studio .NET. Both integrated development environments offer a host of options to simplify test enhancement, including a helpful code-complete feature that suggests code to accelerate editing. GUI developers will find this feature particularly useful, as they can access it within the IDE they use to build the user interface.
10.Linux test editing and test execution support –
For cross-platform Java applications, IBM Rational Functional Tester offers scripting to create, edit, and execute tests on the Linux platform - including everything except a test recorder. It also supports the Windows platform for all recording, editing, and execution capabilities.
11.Add-on support available for testing 3270/5250 terminal-based applications –
Teams responsible for testing mixed workload environments - environments comprised of both Java/Web/Visual Studio .NET-based applications and mainframe-based applications - can purchase the IBM Rational Functional Tester Extension for Terminal-based Applications. This extension enables automation and testing for 3270 and 5250 terminal-based applications, including automated data entry and response verification, using the testing tool and scripting language the tester favors for Windows and Linux-based applications.
12.Extended automated functional and regression testing for Siebel® and SAP® applications –
IBM Rational Functional Tester Extension for Siebel Test Automation interfaces to provide robust automation support for both Siebel 7.7 and 7.8. IBM Rational Functional Tester Extension Automated test creation, execution and analysis of SAP GUI applications.
http://www.qacampus.com
http://www.crestech.in
http://www.crestechsoftware.com.au
Subscribe to:
Posts (Atom)