Can anyone tell how to determine what to test first?
Thanx
Jenita

If any application is given to you how do you start testing? Which type of testing is first carried out for any client-server or web based application?

Please explain me in details.

See it depends on that at which level you get the application.
If you get it complete in all aspects then of course you have to start with functionality testing with positive test cases.

__________________
--
Brijesh Jain

The Application which is assigned for testing is irrespective. It depends on the setup, guidelines, frameworks etc. If the application has the Specification Doc, SRS (Software Req. Specification), Functional Doc...etc. Then you are known that you should start with so and so testing first.

If nothing is provided to you and still you need to test the application, then Exploratory Testing is the first step to start. From this you get to know the application behaviour / Functionality. Then you go-ahead with remaining testing methods.

Hope you got answer

Thanks & Regards

Arun

Testing should be started as follows when a new build is given for testing
1. Smoke Testing should be done first in order to see if any showstoppers are there in the application.
2. If there are no showstoppers then start Functional Testing with execution of testcases.
3. Integration Testing between modules shuld be tested with execution of Integration testcases.
4. If every thing goes fine with th build start System Testing

Please correct me if am wrong.

I strongly agree with satishlingala

__________________
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.

-sutnarcha-

Absolutely correct.....

But this is only for a Functional Testing Purpose. If the application is given for Performance testing then....
First a Smoke Test is needed, then a proper Load Test or a Stress Test

Performance Testing will be started only after functinla testing is completed. So again smoke testing will not come into picture.
Start performance (load or stress or volume) as per the documentation prepared for it.

Actually Integration testing is a whitebox testing, how it is done by black box tester?

Integration testing is not only white box testing.Black box Integration testing is also performed to uncover errors which can't uncover using white box testing.

__________________
--
Brijesh Jain

It depends on the requirement how the client or the project specification document says.

But in general obviously it starts of with usual White box testing from developer's end. Then once the integration testing is done at developer;s end. They check for system(application) stability which is feasible for testing further. Once the builds and everything goes. Then they certify for Blackbox testing where different types of testing is conducted. Like.. It starts with Functional Testing, Regression (if bugs logged and fixed...bug life cycle goes), then system testing (Load, Performance, security, volume...etc), Alpha testing, beta testing..etc and goes on.

Hope you got the answer. But everything is studied, planned accordingly when you kickoff project. At that time the QA Manager, Business Analyst, Project Manager...etc will have a discussion on different types of activities which they need to perform on project and they decide on resources, estimations ...etc and there it goes.

Thanks & Regards

Arun*
BOSTON, MA - 01752

For any type of application firstly we have to test by giving some samples of data so that 90% of errors can be reduced.

by using white box testing only we cannot remove the errors. This type of testing is used for any logical errors, input errors etc.. But the black box testing identifies all the system errors.

Hi Guys,
I registered to this forum just last week. As my first attempt i will try answer to this question.

I feel your question should be clear like..is it testing carried out during coding(white-box testing) or after coding(system testing).

Let me clear this to you. Basically we can isolate this into 2 categories of testing 1. Pre-System Testing
2. System Testing.

Pre-System Testing: Usually this testing is carried out before the actual application comes to system testing. In this we will be involved in testing at various phases like
a. Requirements Testing called Requirements Verification
b. Design Testing called Design Verification
c. Code testing called white-box testing which is termed as unit testing.

Requirements Verification can be carried out by the dev team and also by testing team to ensure all requirements are covered and captured based on the business requirements and other stakeholders.

The same way design verification can be carried out by dev team and design expert relevant to the technology.

Once these 2 verifications are finished then comes unit testing which will be carried out by dev team as peer & external reviews. Once all these are completed then the application is ready for actual testing by testing team.

System Testing: In this testers can carry out various types of testing based on the application. Like Smoke testing, Sanity testing, Functional testing, Regression testing and Retesting.

The above specified types of testings can be carried purely if you have detailed requirements in place and testcases drafted based on them.

Few more types of testings can be carried out like exploratory testing and retesting if requirements are incomplete or available at high-level. Because tester will not be able to document testcase in detailed based on these incomplete requirements. So during his test execution what ever testcases he come across and based on the impact they will be added to the testcase design as negative scenarios.

This is the detailed explanation on types of testings. Again coming to your Question if it is related to testing carried out by testers then the first testing that we carry out is SMOKE Testing. Once this is passed then the next level is either we do SANITY testing or we continue with actual FUNCTIONAL Testing followed by Regression Testing and Retesting.

In SMOKE Testing (very First Testing) we will ensure that the minimum critical functionalities of the application are passed.

But we dont have SMOKE Testing as first testing when the application do have incomplete and high-level requirements. In this we start directly with Exploratory Testing i.e directly hitting the application following few methods like ADHOC, MONKEY, FREE-LANCE Testing.

Once all these are completed and tester approves the quality of the application as good, then if project demands we will be doing NON-Functional Testings called PERFORMANCE, SECURITY, USABILITY Testings.
.

I hope i answered your question. For any clarifications you can ping me at idreams27@yahoo.com

Thanks
Narasimha Reddy

It depends on the requirement, specification document which is obtained. Everything is mentioned in the document. What and which type of testing is to be carriedout.

Basic testing should be performed this everyone knows. But the one which should be started depends on application/product, client requirement..etc. Either you go for whitebox or blackbox testing. But both are compulsory to test for its feasibility.

Arun

Hi everybody


Can anybody tell me mostly used testing types?

Functioal and usability.

__________________
--
Brijesh Jain

The Seq is :

1. Unit
2. Integration
3. Smoke
4. Functional
5. AD hoc
6. Performance
7. Stress

This is normal sequence in any place with little improvisation or Adjustment

can anyone tell me hw to write test conditions and test cases using use cases

Once we recieve build from PM, at first we have to carried out Sanity testing in order to check the application whether are there any showstopers occur,whether the application is operatable, observable, consistency and whether it is installed correctly or not and also whether it is stable to continue further testing.

Once we get stable build then we can go for functionality testing with +ve test cases as well as -ve test cases to check that the application is working functionally(like calculations, input domain, out put domain, error handling...etc) or not

And then Retesting (for confirmation to check that whether the fixed bug is correctly solved by giving same i/p values or different input values according to customer reqs) and Regression testing (for confirmation to check that whether there are any side effects occured on existing functionality due to bug fixuation)

then user acceptance testing(alpha testing), port testing, deployment testing and beta testing.

let me know if it is any wrong.
Bharathi

First we will do Smoke Testing .