manual testing procedure

I am new to testing, could someone please tell me the step by step procedures to go about in manual testing? how is it done in real world?

Hi.
Welcome to the testing world :-)
I hope u have clear idea about SDLC.Almost same life cycle should be follwed in testing life cycle also starting from requirement gatharing to bug fixing.
i am trying to give you some idea abt this cycle,some steps might be missed:
1.Testing requirement gathering
2.Testing requirement analysis
3.Sign Off requirement
4.Test strategy fixing
5.Preparing Test Cases
6.Review and freeze test cases
7.Execution of test cases
8.Report the bugs
9.Fixing the bugs
10.Retest and close the bugs
11.Prepare the defect summary report

hope i have covered almost all the steps.
Please reply back if you need more information.

Thanks.
Chiranjib.

hi there,
well im new to testin area...could u plz tell me wt is SDLC or SDLC processes ??
thanks & regards,
inder

Hi inder sdlc means software development life cycle this has the following activities. 1. Software requirements analysis 2. Systems analysis and design 3. Code generation 4. Testing 5. Maintenance

Hello to geekinterview.

i would to write online testing on manual tasting.

[b][b]manual test organization[/b][/b] test team leader ----> sets test strategy---->mission/business analysts --->test objectives ----->test analysts/designers----------> manual test cases and scripts---->testers please reply back if you need more information. Thanks ram

After approal of the project BA will release the SRS. Testers and developers go through this document. Later they will conduct a meeting in this meeting if u have any doubts in SRS regarding terminalogy or confussion sentences they will clarify and some times they will send a template with SRS u have doubts u can write and send to BA.Mean time senior people will prepare like test leads,UCD usecase document.with this Business rules will be attached. Based on these two testers have to develop test cases in the given test case templete. while developing the test cases whenever required u have to apply business rules and while preparing test data BVA AND ECP have to apply. After the build is released tester has to execute the test cases. If they found the bug they send to the leads if it is rellay a bug it is open this bug when tester found its status is new. After bug is rectified againg we have to test the total functionality. Who have clear idea in the project they may involve insystem testing it will do after deployment . after total modules were developed all the modules are integrated. this done before system testing. At last database testing will be done.



Test metrics will be prepared by testers.

Testing is method to verify and validate that the system or application under test performs as per the requirements.

Manual Testing is the means by which the System is tested manually without the use of any Automation Tools. The system can be tested for its Functionality and its Performance.

As per the SDLC the Testing starts after the Development. The simple Life cycle of a Software is
Requirement --> Design --> Coding / Development --> Testing --> Implementation --> Maintenance.

The Testing activity will begins once after the Requirement is done. The Testing starts of with the analysis of the Test requirement. Once the analysis is done, the estimation and schedule is done for the duration of testing activity. Then the Requirements are splitted into smaller parts as Test cases, which will reviewed by the senior members and business analysts. The Test case is a template having the Description, The testing action, Expected result and the Actual Result column. Once the application is ready for testing the test cases are executed against the application and the actual results are recorded. If the actual result varies from the expected one the test cases fail and the defects are logged. And after the defects are accepted it will fixed and then retested, if the defect is validated is closed. This activity is carried till the defects are closed.

This is the approach that are carried out in Manual testing. I hope you get some knowledge regarding manual testing.

Ganesan R

Following is the procedure must followed in manual testing 1. Tester should go through requirement documents.(requirement analysis) 2. Go through the documents which are created by developers. 3. Create the test plan on the basis of both documents. Test plan includes: 1. Objective 2. Scope 3. Area of focus 4. Time estimation - how much time required to test 5. Resources: how many team members are included in testing. 4. Create the detail level test cases including all the testing scenario's (positive+negative) 5. After creation of test case, execute the test cases and verify the actual and expected result. 6. If find any defect then make the entry in the bug tracking tool (like:bugzila) and mentioned the defect number in the test case. 7. After the defect is fix by developer then re-verify the defect and then close the defect. I have mentioned the steps which we followed in our company. If i am wrong then please correct me and let me know

manual testing steps
1.Requirement gathering
-objective
-entry criteria
-activities
-exit criteria
-risk based testing
-test requirement management
test strategy
-configuration matrix
-critical sucess factor or quality sucess factor
a.usability
b.maintability
c.scalability
d.portability
-issue escalation/problem reporting
-risk and action plan
-defect reporting process
-test environment
-measurement techniques
test planning
-system description
-scope of testing
a.inscope of testing
b.out of scope of testing
-schedules and time lining
a.over all status
-training plan
-estimations
-client deliverables
-risk and action plans
a.risk portability
b.risk impact
c.risk exposure value
-roles and resposibility
a.roles of test manager
b.roles of test lead
c.roles of test engineers
test design
-usecase design/analysis
-scenarions identification
-test case preparation
test execution

pls inform me if any thing is wrong in my answer

manual testing procedure basically consist of a set of activities which include (i)the detailed analysis of the Software Requirement Specification of the software.
(ii)On the basis of SRS prepare the test Plan
(iii)Prepare the test cases.
(iii)Execute the test cases.
(iv)Analyze the result.
(v)Report the Bug If Found.
...........

I am new to testing, how much time to take a testing for simple master form in manual testing

[QUOTE=riyazedkal;32574]I am new to testing, how much time to take a testing for simple master form in manual testing[/QUOTE]
I am new to testing, how much time to take a testing for simple master form in manual testing

Hi riyazedkal,

Here is the Article i found for the time schedule for testing ,this article is based on time schedule for web testing.

This question pops up in various forms all the time. It boils down to "We don't have enough time to test everything, so what do we test?" Not having enough time, of course, is not only the status quo for testing software, it is a universal truth for any software that will ever go into production.
Given that, here's my advice.


1.Start by forgetting that you have any test cases at all.

2.Make a list (quickly -- remember we don't have enough time to test, so let's not waste what little time we have making lists) of each of the following usage scenarios. I usually limit myself to five on the first pass, but no matter what, move on to the next category as soon as you find yourself thinking about the category you are on. If you have to stop and think, whatever you come up with isn't important enough.

a.What things will users do most often with this application?
b.What areas of this application are most likely to contain show-stopping defects?
c.What parts of this application are critical to the business?
d.Are any parts of this application governed by legal or regulatory agencies?
e.What parts of the application would be most embarrassing to the company if broken?
f.What parts of the application has my boss said must be tested?

3.Prioritize the list. If you've made the list in a word processor or using note cards, this will take under 60 seconds (if you have to write a new list by hand and you write as slowly as I do, it will probably take a little longer. Here are the rules for prioritizing.

a.Count the number of times a scenario appears in any of your categories. The more times the scenario appears, the higher the priority.
b.In case of a tie, 'a' comes before 'b' comes before 'c,' etc.

4.Now scan your test cases. Note which ones are covered and which ones aren't. On the ones that aren't covered, ask yourself, "Can I live with not testing this?" If the answer is no, add it to the bottom of the list.

5.Start testing.

6.If you complete these tests before time is up, do the same exercise again without repeating any usage scenarios. If not, at least you have a defensible list of what you did and did not test and lost all of about 15 minutes of testing time creating that list.

In case you're wondering, this approach is derived from my FIBLOTS heuristic for deciding what usage scenarios to include when developing performance tests. FIBLOTS is an acronym representing the words that complete the sentence "Ensure your performance tests include usage scenarios that are:

• Frequent
• Intensive
• Business critical
• Legally enforceable
• Obvious
• Technically risky
• Stakeholder mandated."

I guess for functional testing, it would be "Ensure you test usage scenarios that are:

• Frequent
• Risky
• Business critical
• Legally enforceable
• Obvious
• Stakeholder mandated."

Too bad the acronym FRBLOS isn't as easy to remember as FIBLOTS.

Also please find the file attached

Hi,
Iam doing manual testing from last month.Now I want to learn QTP.Is it possible to learn QTP by open source.
Please suggest.
And please let me know some information regarding QTP.

Regards,
Keemo.

hi keemo,

It is possible to learn QTP , because along the mercury product you have inbuilt documentation which helps you to learn quickly

Thanks
Deepasree

how to become master in manual testing. that is writing test cases..etc,

hi kesuma,

I hope u know the procedure for writing test cases and only real time experience make you master in manual testing

Thanks
Deepasree

Hi all,
i wanna to move automation so how i can start it.........?

hi i am new to manual testing can anyone say that waht are the general guideline when testing a form in business application

[QUOTE=indersivia;9640]hi there,
well im new to testin area...could u plz tell me wt is SDLC or SDLC processes ??
thanks & regards,
inder[/QUOTE]

SDLC:
Software development life cycle
we have diferent SDLc models
waterfall and V model most of the companies are following
water fall model is used for small projects where requirements r very clear.
for big companies they follow V model
In SDLC model,
Requirements
Review of requirements
designing test cases
exicuting test cases
installation maintenence

for testing ppl u should also know about STLC(Software testing Life Cycle)
below mentioned points will come under STLC.
Requirements (Soft wareRequirement Specification)
Review of the requirements(will review the requirements which r not clear and which r not able to understand).
Designing test cases
Exicuting test cases
Reviewing test cases(here two kinds of reviews are there 1.With in the team other ppl will review our test cases and 2.people who are not related to our application will review our test cases)
Bug report
Closing bugs
Status report.

Hope my answer is correct if i am wrong please correct me.......

[quote=jyoti akella;20119]manual testing steps 1.requirement gathering -objective -entry criteria -activities -exit criteria -risk based testing -test requirement management test strategy -configuration matrix -critical sucess factor or quality sucess factor a.usability b.maintability c.scalability d.portability -issue escalation/problem reporting -risk and action plan -defect reporting process -test environment -measurement techniques test planning -system description -scope of testing a.inscope of testing b.out of scope of testing -schedules and time lining a.over all status -training plan -estimations -client deliverables -risk and action plans a.risk portability b.risk impact c.risk exposure value -roles and resposibility a.roles of test manager b.roles of test lead c.roles of test engineers test design -usecase design/analysis -scenarions identification -test case preparation test execution pls inform me if any thing is wrong in my answer[/quote] you have to tell about the procedure only.. Not about the roles i think it is clear na.... If i impair you... Sorry... Have a beautifull day.

[QUOTE=penisetty;54753]you have to tell about the procedure only.. Not about the roles i think it is clear na.... If i impair you... Sorry... If you want more knowledege then call me . Have a beautifull day.[/QUOTE]

hi penisetty,

Again you can post the answer in the forum itself.

Thanks,
Deepa

[QUOTE=rvija;8961]I am new to testing, could someone please tell me the step by step procedures to go about in manual testing? how is it done in real world?[/QUOTE]


Hi,
As a tester, the first thing to be noted is the way you see should not be same as a developer. you should analysis the Problem in different angle. you should not write the test scenario/testcase as per developers view. you should be clear with requirment and your test scenario/testcase should be manner to test the changes both in Positive and negative manner. once you found the bug you should report to ur test lead. then in turn discuss with functional analyst/business analyst. If it is found that it does not meet the requirment, you should raise the bug.

HI,

Please find following STLC
===================


[B] Life Cycle of Testing Process[/B]

in Each phase of the development process will have a specific input and a specific output.
Once the project is confirmed to start, the phases of the development of project can
be divided into the following phases:

1.Software requirements phase.
2.Software Design
3.Implementation
4.Testing
5.Maintenance


In the whole development process, testing consumes highest amount of time. But most of the developers oversee that and testing phase is generally neglected. As a consequence, erroneous software is released. The testing team should be involved right from the requirements stage itself.



The various phases involved in testing, with regard to the software development life cycle are:

1. Requirements stage
2. Test Plan
3. Test Design.
4. Design Reviews
5. Code Reviews
6. Test Cases preparation.
7. Test Execution
8. Test Reports.
9. Bugs Reporting
10. Reworking on patches.
11. Release to production.



[B]Requirements Stage[/B]
Normally in many companies, developers itself take part in the requirements stage. Especially for product-based companies, a tester should also be involved in this stage. Since a tester thinks from the user side whereas a developer can’t. A separate panel should be formed for each module comprising a developer, a tester and a user. Panel meetings should be scheduled in order to gather everyone’s view. All the requirements should be documented properly for further use and this document is called “Software Requirements Specifications”.







[B] Test Plan[/B]
Without a good plan, no work is a success. A successful work always contains a good plan. The testing process of software should also require good plan. Test plan document is the most important document that brings in a process – oriented approach. A test plan document should be prepared after the requirements of the project are confirmed. The test plan document must consist of the following information:

• Total number of features to be tested.
• Testing approaches to be followed.
• The testing methodologies
• Number of man-hours required.
• Resources required for the whole testing process.
• The testing tools that are to be used.
• The test cases, etc



[B]Test Design[/B]

Test Design is done based on the requirements of the project. Test has to be designed based on whether manual or automated testing is done. For automation testing, the different paths for testing are to be identified first. An end to end checklist has to be prepared covering all the features of the project.

The test design is represented pictographically. The test design involves various stages. These stages can be summarized as follows:

• The different modules of the software are identified first.
• Next, the paths connecting all the modules are identified.

Then the design is drawn. The test design is the most critical one, which decides the test case preparation. So the test design assesses the quality of testing process.



[B]Test Cases Preparation[/B]
Test cases should be prepared based on the following scenarios:

• Positive scenarios
• Negative scenarios
• Boundary conditions and
• Real World scenarios

[B]Design Reviews[/B]

The software design is done in systematical manner or using the UML language. The tester can do the reviews over the design and can suggest the ideas and the modifications needed.



[B]Code Reviews[/B]
Code reviews are similar to unit testing. Once the code is ready for release, the tester should be ready to do unit testing for the code. He must be ready with his own unit test cases. Though a developer does the unit testing, a tester must also do it. The developers may oversee some of the minute mistakes in the code, which a tester may find out.



[B]Test Execution and Bugs Reporting[/B]
Once the unit testing is completed and the code is released to QA, the functional testing is done. A top-level testing is done at the beginning of the testing to find out the top-level failures. If any top-level failures occur, the bugs should be reported to the developer immediately to get the required workaround.

The test reports should be documented properly and the bugs have to be reported to the developer after the testing is completed.



[B]Release to Production[/B]
Once the bugs are fixed, another release is given to the QA with the modified changes. Regression testing is executed. Once the QA assures the software, the software is released to production. Before releasing to production, another round of top-level testing is done.

The testing process is an iterative process. Once the bugs are fixed, the testing has to be done repeatedly. Thus the testing process is an unending process.


Thanks,
Mahantesh.G.Hadimani