Friday, September 7, 2012
How will you handle Java tree in QTP?
Posted by
Sunflower
at
9/07/2012 02:30:00 PM
0
comments
Labels: Add-ins, Application, Automated, Automation, Data, Database, Elements, Hierarchical, Identification, Java tree, Nodes, Objects, QTP, Queries, Quick Test Professional, Software System, Tasks, Testing tools
|
| Subscribe by Email |
|
Saturday, July 21, 2012
What is meant by DNS? What does it contain?
- Computers
- Services
- Resources that
are connected to some private network or internet and so on.
What does DNS contain?
Posted by
Sunflower
at
7/21/2012 10:56:00 AM
0
comments
Labels: Address, Communication, Distributed system, Domain, Domain Name, Domain Name System, End users, Functionality, Hosts, Information, Internet, IP address, Network, Protocol, Queries, Register, Resources, Servers, URL
|
| Subscribe by Email |
|
Friday, April 13, 2012
What is a mock object? What are the reasons for use?
Perhaps most of us have heard about mock objects but do not know what it is actually! This article is dedicated to the mock objects and the reasons for which they are used.
First we will clear up the concept of mock object and then we will move on to the reasons for its use. Mock objects are a concept of the object oriented programming.
" Mock objects are defined as some simulated objects that have the ability to mimic the behavior of the real objects in a defined and controlled way. Mock objects are used by a programmer or developer to check another object by testing it against the mock object."
Reasons for use of mock objects
- Mock objects as we discussed above are able to perfectly simulate the behaviour of real or we can say non- mock object be it very simple or very complex.
- This property of the mock objects make them an essential and convenient tool for carrying out an effective unit testing which involves testing of the software program modules in isolation.
- It should not be mistaken that the mock objects are used in the place of the original non mock objects.
- They are used in their place only during the testing phase and that too when it is almost impossible and impractical to incorporate the real object in to the created unit tests.
- In some of the cases it is required the presence of some object for testing another one. In such cases the mock objects play a very important role.
Characteristics of Mock Object
Below mentioned are some characteristics which if are present in a non mock object, it is important that you use a mock object in its place:
1. If the object supplies non deterministic results such as the current temperature and current time etc.
2. If the object is having states that are somewhat difficult to be reproduced and recreated such as a network error and so on.
3. If the object is too slow i.e., if it is having a complete data base which requires initializing before the starting of the test.
4. If the object does not exist in practical.
5. If the object tends to change its behavior.
6. If the object currently does not exists.
7. If the object requires including the methods and information regarding the testing purposes but not its actual tasks.
8. If the object is difficult to set up.
9. If the object is a user interface.
10. If the object cannot be queried.
We will give an example so that the mock object concept becomes clear to you!
- Consider your mobile alarm clock which causes an alarm bell to ring at the time that you specify.
- Suppose it gets the current time from somewhere outside, then how do you test this mobile alarm?
- You will have to wait till the alarm bell goes off till that specified time to check whether or not the mobile alarm is working correctly or not.
- Mock objects are sometimes used as mediators.
- In such cases a mock domain comes in to play rather than the actual domain.
Features of Mock Object
Below mentioned are some of the features of a mock object:
- Easy to create
- Easy to set up
- It is quick
- Deterministic
- Easy to cause behavior
- Does not have any direct user interface
- Can be queried directly
The mock objects did not come in to existence in a single day. It took a whole lot of days to experiment, discuss and collaborate and put forward the idea of using a mock object.
Posted by
Sunflower
at
4/13/2012 11:30:00 PM
0
comments
Labels: Behavior, Characteristics, Create, Data, Easy, Errors, Features, Interface, Mock, Mock objects, Network, Phases, Queries, Reasons, Software testing, Stimulation, Tasks, Uses
|
| Subscribe by Email |
|
Wednesday, March 14, 2012
What are major activities in database testing?
Before going to the main topic i.e., the major activities that are carried out in data base testing, we will first have an insight on what is data base testing actually.
WHAT IS DATABASE TESTING?
- Data base testing as it suggests itself, it is the testing of the data or values retrieved from the data base of that software system or application under testing.
- The retrieved data should match exactly with the data mentioned in the records of the data base.
- Data base testing is not an easy thing to carry out.
- It calls for a great need of expertise in reading the data base record tables, writing procedures and queries for the data base.
- Data base testing works well with all sorts of application softwares be it any application written either in SQL or Oracle languages.
- But normally, data base testing finds it way in the testing of applications that work with all sorts of sensitive data like finance, banking or health insurances etc.
- Such applications require extensive data base testing since any error in the retrieved data can cause the users lot to suffer.
MAJOR ACTIVITIES OF DATABASE TESTING
Now we are going to discuss about the working of the data base testing or what all are the major activities taking place in a data base testing.
- A lot of understanding and knowledge of the software system or application under the testing is required i.e., the tester needs to know all about the type of data base being used by the software system or application.
- All the existing data tables in the application data base are figured out.
- All the possible queries are written for the figured out tables to be executed.
- All the tables are tested individually for the verification and validation of the data contained in them.
- For complex data bases the queries are obtained from the developer and the functionalities are tested.
- The data base of a software system or application is indeed its back bone and needs to be tested thoroughly.
- In a data base testing not only the data base undergoes testing, but also the features and functionality of the software system or application.
- As if this is not enough, all the actions taking place like deletion or addition are also tested.
- The added values or data are checked against the records of the data base i.e., whether or not they are exactly same.
- The deleted is checked for whether or not it has been really deleted from the data base.
- Every action being performed is tested for its efficiency as it will affect the overall well being of the data base.
- These days with the introduction of the business logic, the data bases have become more complex.
- Though the business logic makes the whole data base complex in nature, it cannot be neglected since it plays a very crucial role in the implementation of the applications.
- After the implementation of the business rules or logic, the data base values are again checked for their correctness.
- The coupling of the data bases to the libraries also poses a problem for the data base testing besides the following:
1. Data base schemas
2. Data base tables
3. Verification of the data base after every execution of test cases.
4. Cleaning up of the data base for every new test case execution.
5. Carrying out the whole data base testing manually is absolutely impossible or perhaps a nightmare.
6. Writing short test codes that are easy to understand.
One needs to carry out data base testing very carefully and with understanding since any faltering can disrupt the whole testing process.
Posted by
Sunflower
at
3/14/2012 11:17:00 PM
0
comments
Labels: activities, Addition, Application, Complex, Data, Database, Database Testing, Defects, Delete, Deletion, Errors, Features, Functionality, Queries, Records, Software testing, SQL, Tables, Tester, Tests
|
| Subscribe by Email |
|
Saturday, October 1, 2011
Estimation Techniques - For Web Engineering Projects
Early estimation is required during planning even though there is a huge chance that these are proven wrong. Some uncertainty is unacceptable and some solid techniques and concrete procedures help reduce the inaccuracy of estimates.
Estimating techniques for web engineering projects adapt the agile process model. Along with the agile estimation approach, a modified function point (FP) measure can be used to develop an estimate for a web application. Roetzheim suggests for web application estimation, the information domain values while adapting function points are:
- Inputs include maintenance screen, input screen or form or each tab using a tab notebook.
- Outputs include static web page, dynamic web page script, each report whether web based or administrative in nature.
- Tables include logical tables in database, each XML object if XML is used to store data.
- Interfaces are logical files into our out of the system boundaries.
- Queries are a message oriented interface and they are externally published.
According to Mendes:
The best way to determine the volume of the web application is by :
- predictor variables that are associated with application like page count, function count, media count,
- web page characteristics like page complexity, linking and graphic complexity,
- media characteristics like media duration,
- functional characteristics like code length.
Empirical estimation models for:
- total project effort
- page authoring effort
- media authoring effort
- scripting effort
can be evaluated by using these measures.
Posted by
Sunflower
at
10/01/2011 02:57:00 PM
0
comments
Labels: Characteristics, Cost, Effort, Estimates, Estimation, Inaccuracy. Inputs, Interfaces, Media, Outputs, pages, Queries, Script Language, Tables, Techniques, Web Applications, Web pages
|
| Subscribe by Email |
|