Sunday, June 23, 2013
Explain the various File Operations
Posted by
Sunflower
at
6/23/2013 10:30:00 AM
0
comments
Labels: Abstract, Attribute, Contents, Create, Current, Delete, File Operations, files, Input, Location, Operating System, Operations, OS, Output, Pointer, Process, Re-position, Read, Truncate, Write
| Subscribe by Email |
|
Wednesday, May 15, 2013
What is the Process Control Block? What are its fields?
Posted by
Sunflower
at
5/15/2013 06:09:00 AM
0
comments
Labels: Classes, CPU, Create, Data, files, Input, Kernel, Memory, Multi-tasking, Operating System, Output, PCB, Process, Process Control Block, Resources, Structure, Tables, Tasks, update, User
| Subscribe by Email |
|
Tuesday, February 5, 2013
How test cases are generated using Testing Anywhere?
How test cases are generated using Testing Anywhere?
Posted by
Sunflower
at
2/05/2013 03:11:00 PM
0
comments
Labels: Application, Applications, Control, Create, Execute, Machine, Product, Programming, Record, Recording, Remote, SMART, System, Test cases, Testing, Testing Anywhere, Tests, Users, Web, Web Application
| Subscribe by Email |
|
Thursday, November 1, 2012
What is Keyword driven testing? What are base requirements for keyword driven testing?
- Planning phase and the
- Implementation phase
What is Keyword Driven Testing?
Advantages of Key word Driven Testing
- Concise test cases.
- Test cases are readable only by the stake holders.
- Easily modifiable test cases.
- Easy reuse of the existing keywords by the new
test cases.
- Keywords can be re used simultaneously across
multiple test cases.
- Independent of programming languages as well as
specific tool.
- Labor gets divided.
- Less requirement of tool and programming skills.
- Lower domain skills required for keyword
implementation.
- Layer abstraction.
Disadvantages of Keyword Driven Testing
Base Requirements of Key word driven Testing
- Full separation of test development and test
automation processes: The separation of these two processes is very much
required for test automation since both of them have very different skill
requirements. The fundamental idea behind this is that the testers should
not be programmers. Testers should have the ability of defining test cases
which can be implemented without having to bother about the underlying
technology.
- The scope of the test cases must be clear and
differentiated: The test cases must not deviate from their scope.
- Right level of abstraction must be used for
writing the tests: Tests must be written at levels such as lower user
interface, higher business level etc.
Posted by
Sunflower
at
11/01/2012 06:31:00 PM
0
comments
Labels: Advantages, Automated, Automated Testing, Automation, Base, Create, Creation, Design, Disadvantages, Implementation, Keyword driven testing, Phases, Planning, Requirements, Software testing, Test cases, Tests, Tools
| Subscribe by Email |
|
Saturday, October 13, 2012
What are file types used in Silk Test?
- Test plan (.pln): This file
type in silk test facilitates the creation of the test suites. But the
test suites can be created lonely if this file type is combined with the
test scripts.
- Test script (.t): This file
type in the silk test is used while writing the actual test scripts. Whenever
such a file is in run session the test one and test two test cases are
executed by it in a predefined order and at the end the note pad application
is closed.
- Frame file (.inc): The windows
and the controls present in the AUT or application under test are defined
by an abstraction layer. These windows as well as the controls are
referenced later in .t files.
- Result file (.res): This file
type consists of all the test run results which have the names of all the
passed as well as failed tests along with their suitable descriptions. These
file types may or may not contain log messages.
- ANSI format or
- The UTF – 8 format
- Project (.vtp): This file type is saved with an extension of 'verify test project' and
is used as storage for the locations as well as the names of the files
that are currently in use by some project. With this file type there is
another associated file type .ini extension since it is an initialization
file.
- Data driven script (.g.t): This
file type stores the data driven test cases which are use to pull out data
from the data bases.
- Suite (.s): With the help of
this file type the sequential execution of several test scripts is
possible.
- Text file (.txt): This is an
ascii file type and can be used for the following purposes:
- When the files are loaded or
- When any change has occurred in
the file types.
Posted by
Sunflower
at
10/13/2012 02:37:00 PM
0
comments
Labels: Application, Automated Testing Tools, Automation, Controls, Create, Data-driven, Database, Fail, files, Frames, Purpose, Result, Scripts, SilkTest, Software testing, Test cases, Test Scripts, Test Suite, Types, Window
| Subscribe by Email |
|
Wednesday, September 12, 2012
What are Virtual Objects in Quick Test Professional?
- It is not possible
to use the object spy on a virtual object.
- Only recording
operation can be performed on virtual objects.
- You cannot treat
labels and scroll bars as virtual objects.
- Analog recording and
- Low level recording.
Posted by
Sunflower
at
9/12/2012 11:45:00 PM
0
comments
Labels: Actions, Application, Automated, Automated Testing Tool, Automation, Create, Errors, Objects, Operation, Properties, QTP, Quick Test Professional, Recording, Records, Run, Scripts, Tools, Users, Virtual, Virtual Object
| Subscribe by Email |
|
Sunday, August 19, 2012
How do you program tests with Test Script language (TSL)?
- Variables
- Control flow
statements
- User defined
functions
- Arrays and so
on.
- Analog
functions
- Context
sensitive functions
- Customization
functions and
- Standard
functions.
How TSL can aid in the creation of tests?
Posted by
Sunflower
at
8/19/2012 10:59:00 PM
0
comments
Labels: Application, Automated System, Automated Test Generation, Automation, Code, Create, Debug, Design, Functions, Languages, Object, Scripts, Software System, Statements, Test Script Language, Tests, TSL, WinRunner
| Subscribe by Email |
|
Friday, August 10, 2012
What are the benefits of creating multiple actions within any virtual user script?
What is Virtual User?
- Clicking
the mouse
- Hovering
or pointing the mouse over some object on the screen.
- Typing
the words and commands.
- Selecting
some object.
Benefits of creating multiple actions with virtual user script
- Creating
multiple actions within a VU script becomes quite effective when employed
in tests that are highly repetitive and consist of many variations.
- With
the multiple action feature, more and more tasks can be performed which
otherwise would be quite a tedious job to do for the human users. But for
a system it is possible since it does not bother itself with tiredness,
tediousness and thus proving itself as an ideal tester.
- Another benefit of
the multiple actions in one virtual user script is that such tests can be
created which can be run at almost every internal build of the software
system or application under question in the stages like:
- With a virtual user
script with multiple actions it can be easily verified that no
functionality was broken by the code changes that were made to the earlier
version of the software system or application.
- With the help of
multiple actions containing virtual user scripts, an automatic bug verification
mechanism can be set up by imitating the steps through which a bug can be
reproduced.
- The automatic big
verification test thus developed can be used to test each and every
release of the software system or application thus ensuring that the bug
has been fixed and there are no chances of it sneaking back in to the
program code.
- These multiple
actions scripts can be split in to single ones whenever required.
Posted by
Sunflower
at
8/10/2012 12:00:00 PM
0
comments
Labels: Actions, Application, Automatic, Bugs, Create, Functionality, Multiple, Scripts, Software System, Software testing, Steps, Tasks, Tester, Tests, Time, Users, Virtual, Virtual user, Virtual user script
| 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 21, 2012
Data flow testing is a white box testing technique - Explain?
A program is said to be in active state whenever there is some data flow in the program. Without having the data flowing around the whole program, it would not have been possible for the software systems or application to do any thing.
Hence, we conclude that data flow is an extremely important aspect of any program since it is what that keeps a program going on. This data flow also needs to be tested like any other aspect of the software system or application and therefore, this whole article is dedicated to the cause of the data flow testing.
What is Data Flow Testing?
- Data flow testing technique has been categorized under the white box testing techniques since the tester needs to have an in depth knowledge of the whole software system or application.
- Data flow testing cannot be carried out without a control flow graph since without that graph the data flow testing won’t be able to explore any of the unreasonable or unexpected things i.e., anomalies that can influence the data of the software system or application.
- Taking these anomalies in to consideration, it helps in defining the strategies for the selection of the test paths that play a great role in filling up the gaps between the branch testing or statement testing and the complete path testing.
- Data flow testing implements a whole lot of testing strategies chosen in the above mentioned way for exploring the events regarding the use of the data that occurs in a sequential way.
- It is a way determining that whether or not every data object has been initialized before it used and whether or not all the data objects are used at least once during the execution of the program.
Classification of Data types
The data objects have been classified in to various types based up on their use:
- Defined, created and initialized data objects denoted by d.
- Killed, undefined and released data objects denoted by k.
- Used data objects in predicates, calculations etc, denoted by u.
Critical Elements for Data Flow Testing
- The critical elements for the data flow testing are the arrays and the pointers.
- These elements should not be under estimated since they may fail to include some DU pairs and also they should not be over estimated since then unfeasible test obligations might be introduced.
- The under estimation is preferable over the over estimation since over estimation is causes more expense to the organization.
- Data flow testing is also aimed at distinguishing between the important and not so important paths.
- During the data flow testing many a times pragmatic compromises are needed to make since there exist so many unpredictable properties and exponential blow up of the paths.
Anomaly Detection under Data Flow Testing
There are various types of anomaly detection that are carried under the data flow testing:
1. Static anomaly detection
This analysis is carried out on the source code of the software program without the actual execution.
2. Dynamic anomaly detection
This is just the opposite of the static testing i.e., it is carried out on a running program.
3. Anomaly detection via compilers
Such detection are possible due to the static analysis. Certain compilers like the optimizing compilers can even detect the dead variables. The static analysis itself is incapable of detecting the dead variables since they are unreachable and thus unsolvable in the general case.
Other factors:
There are several other factors that play a great role in the data flow testing and they are:
1. Data flow modelling based on control flow graph
2. Simple path segments
3. Loop free path segments
4. DU path segments
5. Def – use associations
6. Definition clear paths
7. Data flow testing strategies
Posted by
Sunflower
at
3/21/2012 11:51:00 PM
0
comments
Labels: Anomaly, Application, Create, Critical, Data, Data Flow Testing, Data objects, In-depth, Internal, Paths, program, Software Systems, Strategy, Techniques, Test cases, Tester, White box testing
| Subscribe by Email |
|
Wednesday, December 8, 2010
What are Test Case Documents and how to design good test cases?
Designing good test cases is a complex art. The complexity comes from three sources:
- Test cases help us discover information. Different types of tests are more effective for different classes of information.
- Test cases can be good in a variety of ways. No test case will be good in all of them.
- People tend to create test cases according to certain testing styles, such as domain testing or risk based testing. Good domain tests are different from good risk based tests.
A test case specifies the pretest state of the IUT and its environment, the test inputs or conditions, and the expected result. The expected result specifies what the IUT should produce from the test inputs. The specification includes messages generated by the IUT, exceptions, returned values, and resultant state of the IUT and its environment. Test cases may also specify initial and resulting conditions for other objects that constitute the IUT and its environment.
A scenario is a hypothetical story, used to help a person think through a complex problem or system.
Characteristics of Good Scenarios
A scenario test has five key characteristics:
a story that is motivating, credible, complex and easy to evaluate.The primary objective of test case design is to derive a set of tests that have the highest attitude of discovering defects in the software. Test cases are designed based on the analysis of requirements. use cases, and technical specifications, and they should be developed in parallel with the software development effort.
A test case describes a set of actions to be performed and the results that are expected. A test case should target specific functionality or aim to exercise a valid path through a use case. This should include invalid user actions and illegal inputs that are not necessarily listed in the use case. A test case is described depends on several factors, e.g. the number of test cases, the frequency with which they change, the level of automation employed, the skill of the testers, the selected testing methodology, staff turnover, and risk.
Posted by
Sunflower
at
12/08/2010 12:37:00 PM
0
comments
Labels: Actions, Characteristics, Create, Design, Domain testing, Effective, Functionality, Results, Scenarios, Software testing, state, Test cases, Tests, Types
| Subscribe by Email |
|