Quality Testing

Quality is delighting customers

Sireesha K's Comments

Comment Wall (81 comments)

You need to be a member of Quality Testing to add comments!

Join Quality Testing

At 3:09pm on October 1, 2009, Mary said…
Sirisha, this is out of topic... can u pls tell where u got this babies photo(Profile photo)???
It just resembles my son
At 2:48pm on October 1, 2009, sbharath1012 said…
hi .. would like to knw abt the testing session ?
At 12:26am on October 1, 2009, sbharath1012 said…
Hi , sorry was not online when u pinged me !!
At 9:40pm on September 30, 2009, Vinod said…
Good to see this group here..... keep rocking :)
At 9:24pm on September 30, 2009, chandrasekhar said…
ya its k
At 8:39pm on September 25, 2009, Lawrence said…
oh... i m sorry..
i didnt notice that
take care
At 4:01pm on September 25, 2009, Lawrence said…
i m fine. i m still active in the chat. But u r not there. take care
At 4:07pm on September 24, 2009, Lawrence said…
Hi Sireesha,
How r u?
At 4:20pm on September 22, 2009, Rajendra samal said…
Do u have any knowledge on load runner/QTP??
At 3:42pm on August 29, 2009, Siddiq said…
Hi,
Forward your profile, will forward.
Thanks,
Siddiq
At 3:44pm on August 28, 2009, Siddiq said…
Go for the Walking, can provide reference....

1. Position: Manual Testers
Exp: 2.5 Yrs to 6 yrs
Skills Required: Manual Testing; Exp in any automation testing tools


2. Position: Mainframe Testers
Exp: 2.5 Yrs to 6 yrs
Skills Required: Mainframe Testing

Please upload your referrals resumes at https://careers
At 4:51pm on July 22, 2009, Mohan Bhardwaj said…
Thanks for appreciating my snaps...
At 8:39pm on July 20, 2009, Siddiq said…
Sireesha,
Will upload the information soon, sorry for the delay...

I don't have access from my Office need to find time and get the docs for you...
Thanks,
Siddiq
At 6:49pm on July 20, 2009, srinukotha said…
Thanks for ur co operation
i have some thing with me if necessary i will also fwd the thing which i have..

bye
catch u again
At 4:44pm on July 20, 2009, srinukotha said…
"Never give up the right to be wrong becoz then you will lose the ability to learn newthings and move forward with UR life."
Nice Thought !!!
If u have any thing related QTP send to srinukotha007@gmail.com.
It would be greatful for me to learn Automation.
This is srinu Sr.QA Eng. Indore(MP) previously worked in hyd and native of vizianagaram(AP)

Thanks In Advance
At 11:22am on July 17, 2009, Amit Kulkarni said…
No man... I have seen ur stuff and u r very much active on this site.

Keep it up dude!!!!

Nice talking to u... tc

Amit
At 11:17am on July 17, 2009, Amit Kulkarni said…
Sireesha,

Gotcha!!!!

Automate the things.... if the template is available .. Why not use it?

Amit
At 8:49pm on July 16, 2009, Bhagawati said…
Hi Sireesha,

whenever you will be online in QT, morning 11 to evening 6:30, just give me an email to bhagawati.manukonda@applabs.com, so that i can come online.

Thanks,
Bhagawati
At 4:08pm on July 16, 2009, REDDY SIVA SARAN.K said…
Can I know on what tool u r working currently
At 10:52am on July 15, 2009, Vinayak W said…
Hi Sireesha,

What is a White Box Testing Strategy?

White box testing strategy deals with the internal logic and structure of the code. White box testing is also called as glass, structural, open box or clear box testing. The tests written based on the white box testing strategy incorporate coverage of the code written, branches, paths, statements and internal logic of the code etc.

In order to implement white box testing, the tester has to deal with the code and hence is needed to possess knowledge of coding and logic i.e. internal working of the code. White box test also needs the tester to look into the code and find out which unit/statement/chunk of the code is malfunctioning.

Advantages of White box testing are:
i) As the knowledge of internal coding structure is prerequisite, it becomes very easy to find out which type of input/data can help in testing the application effectively.
ii) The other advantage of white box testing is that it helps in optimizing the code
iii) It helps in removing the extra lines of code, which can bring in hidden defects.

Disadvantages of white box testing are:
i) As knowledge of code and internal structure is a prerequisite, a skilled tester is needed to carry out this type of testing, which increases the cost.
ii) And it is nearly impossible to look into every bit of code to find out hidden errors, which may create problems, resulting in failure of the application.

Types of testing under White/Glass Box Testing Strategy:

Unit Testing:
The developer carries out unit testing in order to check if the particular module or unit of code is working fine. The Unit Testing comes at the very basic level as it is carried out as and when the unit of the code is developed or a particular functionality is built.

Static and dynamic Analysis:
Static analysis involves going through the code in order to find out any possible defect in the code. Dynamic analysis involves executing the code and analyzing the output.

Statement Coverage:
In this type of testing the code is executed in such a manner that every statement of the application is executed at least once. It helps in assuring that all the statements execute without any side effect.

Branch Coverage:
No software application can be written in a continuous mode of coding, at some point we need to branch out the code in order to perform a particular functionality. Branch coverage testing helps in validating of all the branches in the code and making sure that no branching leads to abnormal behavior of the application.

Security Testing:
Security Testing is carried out in order to find out how well the system can protect itself from unauthorized access, hacking – cracking, any code damage etc. which deals with the code of application. This type of testing needs sophisticated testing techniques.

Mutation Testing:
A kind of testing in which, the application is tested for the code that was modified after fixing a particular bug/defect. It also helps in finding out which code and which strategy of coding can help in developing the functionality effectively.

Besides all the testing types given above, there are some more types which fall under both Black box and White box testing strategies such as: Functional testing (which deals with the code in order to check its functional performance), Incremental integration testing (which deals with the testing of newly added code in the application), Performance and Load testing (which helps in finding out how the particular code manages resources and give performance etc.) etc.

Regards
Vinayak

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2020   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service