Pages

Wednesday, April 30, 2008

Test Cover

Hi All,
I happened to read some useful information for the students who have interest over software testing. They can register here and start getting feedback from the site, they have free trial for the same. You can register it from the link given below:

https://testcover.com/pub/students.php

They would help in following areas,
• reducing the number of test cases, and


• improving the test cases' ability to find defects.

GaneshKB

Testing methods

Hi,
Folks, this time i have wikipedia to our help. I found this to be useful, it is all about Software testing methods are traditionally divided into black box testing and white box testing. These two approaches are used to describe the point of view that a test engineer takes when designing test cases. To know more about this, please have look over from the link given here....

Ganesh.KB

I have reached safely...




DEXTER'S BLOG'S

Hi Lab Folks, I have reached safely here....Please find some photos of me here in cold

Wednesday, April 09, 2008

Dexter Flying Abroad

Hi Lab Folks,
I have an update for you all, this is an important news to share with you all. Dexter(GaneshKB) will be in US for the next one year or so, I will be back only by April next year. Until then i will blog from there.

Ganesh.KB

Thursday, April 03, 2008

Hi,
I have another cool site with answers for my previous questions and also few more interview questions with answers for the same,Please click here for the cool site:

Ganesh.KB




Technorati Tags: , , , , , , ,

Wednesday, April 02, 2008

Dexter Mysql tunning

@start "MySQL" /B "%DB_HOME%\bin\mysqld-nt" --standalone --lower-case-table-names=1 --basedir="%DB_HOME%" --port=%DB_PORT% --datadir="%DB_HOME%\data" --default-character-set=utf8 --set-variable=query_cache_type=2 --read_buffer_size=128K --read_rnd_buffer_size=2M --sort_buffer_size=4M --myisam_sort_buffer_size=2M --tmp_table_size=32M --max_heap_table_size=32M --key_buffer_size=8M --innodb_buffer_pool_size=128M --bulk_insert_buffer_size=8M --table_cache=256 --thread_cache=32  --innodb_flush_log_at_trx_commit=0 --low-priority-updates --log-slow-queries --long_query_time=5


 

--query_cache_type : defines whether to cache query results

                             0 - no caching

                             1 - always

                             2 - on demand

 

--read_buffer_size : each user thread use data blocks of this size for read operation.

                            size = 128K - 1M

                            can be increased to a higher value but testing required,

                            increasing might not always gives a positive impact

 

--read_rnd_buffer_size : used by user thread to read data after a sort operation

                                size = 2M - 10M

 

--sort_buffer_size : each thread that needs to sort, allocates a buffer of this size

                         size = 4M - 16M

 

--myisam_sort_buffer_size : buffer size allocated for sorting MyISAM indexes

                                     We use InnoDB

 

--tmp_table_size : Maximum size of a temporary table created.

                        Temporary tables needs to be created during sorting if data set is huge and no indexes can be used

                        size = 8M - 64M

 

--max_heap_table_size : Maximum size of an in-memory table. Generally equal to tmp_table_size

 

--key_buffer_size : Buffer size for storing MyISAM indexes

 

--innodb_buffer_pool_size : Buffer size for storing InnoDB indexes

                                    size = 128M - 50% to 75% of RAM

 

--bulk_insert_buffer_size : Buffer used during bulk insert

                                   will be useful during backup and restore

                                   size = 8M - 16M

 

--table_cache : Opening tables takes time and resources. All indexes realted to the table has to be loaded into the memory. This varibles sets the number of tables to be kept open for further use. Same table opened by two user threads requires two handles.

                    count = 256 - 2048

 

--thread_cache : Creation of thread takes time. No of threads to be pooled for further use.

                       count = 16 - 64

 

--innodb_flush_log_at_trx_commit : determines how redo log buffers are written to the log file

                                               0 - every second

                                               1 - default, on each commit and flush to disk

                                               2 - on each commit, no flush to disk

 

--low-priority-updates : updates have lower priority then read. so an update is blocked until there is a select statement for that table

 

--log-slow-queries --long_query_time=5 : This is analysis only. This will log all queries which take time more then the given seconds (second parameter)

Monday, March 31, 2008

Testing Interview Questions to share

Hi Lab Folks,

I would like to ask few questions, that are kinda mandatory for interview(Experienced candidates):

  1. What is the Difference between Project and Product testing? What
    difference you have observed while testing the Clint/Server application
    and web server application
  2. What are the differences between interface and integration testing?
    Are system specification and functional specification the same? What
    are the differences between system and functional testing?
  3. What is Multi Unit testing?
  4. What are the different types, methodologies, approaches, methods in software testing
  5. What is the difference between test techniques and test methodology?
If any one of you knows answer for the same, Then make comments for the same, Else. I will post them in the next forums.

For more questions, Click here...

Ganesh.KB





Technorati Tags: , , , , , , , ,

Wednesday, March 26, 2008

What is difference between WinRunner and QTP?

Hi Lab Folks,
Cool information about WinRunner and QTP to share with you all.....

1.Winrunner uses TSL language where as QTP uses VB script & Java script

2.Winrunner doesn̢۪t supports the OOPS concept where QTP supports the OOPS concept

3. Winrunner doesn̢۪t supports to multimedia. QTP supports to multimedia , media player , photo shop. (6.5 version ).

4. Winrunner doesn̢۪t supports to XML. QTP supports to XML

5. Winrunner doesn̢۪t supports to .NET. QTP supports to .NET.

6. Winrunner supports only Interpreter ( Line by line execution ). QTP is compiler.

7. In Winrunner GUI spy is used to check the properties of object / window. In QTP,the name is Object spy

8. Winrunner: GUI Map editor is used to store the physical descriptions. QTP: Object Repository is used to store the physical descriptions of the objects

9. Winrunner has 3 modes of recoding :analog and context sensitive recording modes. QTP has only one recording mode i.e Standard recording mode. In this recording 2 types are (1) Analog (2) Low level

10. Winrunner has 4 types of checkpoints [ GUI checkpoint, Bitmap checkpoint, Database checkpoint, Text checkpoint ]. QTP has
9 types of checkpoints [ Standard check point, Bitmap checkpoint,
Database checkpoint, Text/Text area checkpoint, Image checkpoint, Table
checkpoint, Page checkpoint, Accessibility checkpoint, XML checkpoint ]

11. Winrunner: In GUI check point has 3 types
1. single object / single property
2. single object / multiple property
3. multiple object / multiple property
QTP has only One type i.e Single object / Multiple Property

12. Winrunner: In Bitmap checkpoint 2 types
1. for Object / Window
2. for Screen Area
QTP has only One i.e for Object / Window Bitmap using this above checkpoint we can check also Screen area

13. Winrunner: In Database check point there are 3 types
1. Default 2. Custom 3. Runtime
Here in QTP only One Type i.e Custom database checkpoint

14. 9 types of verifications in WR
1. Case Sensitive
2. Case Insensitive
3. Numeric Range
4. Numeric Content
5. Case Sensitive Ignore Space
6. Case Insensitive Ignore Space
7. Exact one match record
8. One or more match record
9. No match record

3 types of verifications in QTP
1. Numeric Range
2. Numeric Content
3. String Content

15. 3 types of Synchronizations in WR
1. for Object / Window Property
2. for Object / Window Bitmap
3. for Screen Area Bitmap
In QTP only One type i.e Object / Window Property

16. WR: Has 3 types of running modes i.e 1.Verify 2. Debug 3. Update. QTP has 2 types of running modes
i.e 1. Standard 2. Update

17. Exception Handling method used to avoid the runtime errors in WR 3 types [ 1. Popup 2. TSL 3. Object ] .In QTP name
is Recovery Scenario and here 4 types of exceptions [ 1. Pop-up Window
2. Object state 3. Test run error 4. Application Crash ]

18. In WR 4
types of result window [ 1. Test result window 2. GUI checkpoint window
3. DB checkpoint window 4. DB record checkpoint window ]. Here in QTP only One Window i.e Test Summary Result Window

19. In WR Test script is divided into 2 parts [ 1. Main Script 2. Compile Module ]. No such types using WR we can execute functions in QTP

20. Add-ins in WR are: 1. ActiveX 2. Power Builder 3. Visual Basic 4. Web 5. Java 6. C 7. C++ , etc Add-ins in QTP are: 1. ActiveX 2. Visual Basic 3. Java 4. Web 5. Multi-media ( 6.5 version )

21. In WR only One View i.e Normal Mode. Here in QTP 2 Views 1. Expert View 2. Keyword View

22.WR: Only One Sheet in data Table if we want to add another sheet then another new data table to be opened. In QTP 2 sheets in Data Table 1. Global 2. Action. In action sheet we can add number of sheets

23. WR: Virtual Object wizard only One type. QTP : 2 types of Virtual Object Wizards [ 1. Virtual Object 2. Virtual Object Manager ]

24. WR: Here after checking the checkpoints it gives mismatch error ( no snap Shots ). QTP: Checks the checkpoint but will not give mismatch error . If test is fail it shows snap shot

25. WR: support Rapid script wizard. QTP: no rapid script wizard

26. Function generator is present in WR. QTP: No Function Generator

27. WR: 2 types of GUI map editor [ 1. Global 2 Per test ]. QTP: only one type i.e Global

28. WR: Only One window I̢۪e Form Window You want to open data table we have to call the function to open data table.
QTP : five types of Window [ 1. Tree View or Keyword view 2. Expert View 3. Data Table 4. Active Screen 5. Debug Viewer ]

29. WR: Running methods [ 1. Step, 2. Step into, 3. Step out ]. QTP : Running Methods [ 1. Step into 2. Step over 3. Step out ]

30. WR: Data type declaration is not necessary. QTP: data type declaration is must

Ganesh.KB


Technorati Tags: , , , , , , , ,

What is Manual testing

Hi Lab Folks,

Manual testing is the oldest
and most rigorous type of
software
testing
. Manual testing
requires a tester to perform manual test operations on the test software
without the help of
Test
automation
. Manual testing
is a laborious activity that requires the tester to possess a certain set
of qualities; to be patient, observant, speculative, creative, innovative,
open-minded, resourceful, unopinionated, and skillful.

As a tester, it is always advisable
to use manual
white
box testing
and black-box
testing
techniques on
the test software. Manual testing helps discover and record any
software
bugs
or discrepancies
related to the functionality of the product.

Manual testing can be replaced by
test
automation
. It is possible
to record and playback manual steps and write automated
test
script
(s) using Test
automation tools. Although, test automation tools will only help execute
test scripts written primarily for executing a particular
specification
and functionality. Test automation tools lack the ability of decision-making
and recording any unscripted discrepancies during program execution. It
is recommended that one should perform manual testing of the entire product
at least a couple of times before actually deciding to automate the more
mundane activities of the product.

Despite the proliferation of automated
solutions, manual testing still accounts for at least 80% of all testing.
Automation can only be justified where repeatable consistent tests can
be run over a stable environment. When this isn't the case (i.e. during
the early stages of the test cycle), then testing teams almost always revert
back to manual testing. So manual testing is here to stay! Here are some
reasons why...

Business critical / Heavily tested
software: With constantly changing applications, automation can simply
be too daunting. New to testing: Those that are new to testing may not
want to dive right in to complex automation tools. Using a tool such as
TestDrive-Assist
[1]
]] can provide an easy and cost effective way to gain real advantages in
a short space of time and use it as a springboard to full automation. Script
based automation tools not living up to their hype: Many people still find
that despite investing in script based automation solutions this only covers
10-20% of their total testing. The rest is still carried out manually.
Full Automation simply not appropriate: You may be testing new functionality,
or a new platforms/OS. Or there maybe insufficient time and/or skills to
develop test scripts. Agile Development: With Agile development techniques,
there is no place for traditional automation tools because they take too
long to set up and need to be re-scripted after the first change to the
application.

Manual testing helps discover defects
related to the
usability
testing
and GUI
testing
area. While performing
manual tests the software application can be validated whether it meets
the various standards defined for effective and efficient usage and accessibility.
For example, the standard location of the OK
button
on a screen is on the left and of CANCEL button on the right. During manual
testing you might discover that on some screen, it is not. This is a new
defect related to the usability of the screen. In addition, there could
be many cases where the
GUI
is not displayed correctly and the basic functionality of the program is
correct. Such bugs are not detectable using test automation tools.

Repetitive manual testing can be
difficult to perform on large software applications or applications having
very large dataset coverage. This drawback is compensated for by using
manual black-box testing techniques including
equivalence
partitioning
and boundary
value analysis
. Using
which, the vast dataset specifications can be divided and converted into
a more manageable and achievable set of
test
suites
.

A manual tester would typically
perform the following steps for manual testing:


1. Understand
the functionality of program


2. Prepare
a test environment


3. Execute
test
case
(s) manually

4. Verify
the actual result


5. Record
the result as Pass or Fail


6. Make
a summary report of the Pass and Fail test cases


7. Publish
the report


8. Record
any new defects uncovered during the test case execution

There is no complete substitute
for manual testing. Manual testing is crucial for testing software applications
more thoroughly. Test automation has become a necessity mainly due to shorter
deadlines for performing test activities, such as
regression
testing
, performance
testing
, and load
testing
.

Ganesh.KB



Technorati Tags: , , , , , , , , , , ,

Tuesday, March 25, 2008

VB Script for QTP

Hi All,
I have another site with loads of information about basic VB scripts and also how we have to use them in QTP. I found it when i was looking to learn more about VB script, as i am also a beginner in it. This stuff is really good, they come with two options one is the basic and the other for advanced on VB scripts. It might be useful do all the LAB folks. You can find the same from, when you click here...

Ganesh.KB


Technorati Tags: , , , , ,