Learn More

Our new digital reading service puts all your favorite documents, news, blogs, friend recommendations and more at arms reach, anytime and anywhere.

Learn More Scribd Upload a Document Search Documents

Top of Form

Bottom of Form

Explore

Documents

Books - Fiction Books - Non-fiction Health & Medicine Brochures/Catalogs Government Docs How-To Guides/Manuals

Magazines/Newspapers Recipes/Menus School Work + all categories Featured Recent

People

Authors Students Researchers Publishers Government & Nonprofits Businesses Musicians Artists & Designers Teachers + all categories Most Followed Popular Sign Up | Log In

1
First Page Previous Page Next Page

/ 88
Sections not available Zoom Out Zoom In Fullscreen Exit Fullscreen Select View Mode

View Mode SlideshowScroll

Top of Form

Bottom of Form

Readcast Add a Comment Embed & Share

Reading should be social! Post a message on your social networks to let others know what you're reading. Select the sites below and start sharing.

Readcast this Document

af5efbe63487914

Top of Form

Login to Add a Comment

4gen
Bottom of Form

Share & Embed

Add to Collections Auto-hide: on

Download this Document for Free

Manual Testing Interview Questions and Answers

What makes a good test engineer?

A good test engineer has a 'test to break' attitude, an ability to take the point of view of the customer, a strong desire for quality, and an attention to detail. Tactand diplomacy are

useful in maintaining a cooperative relationship withdevelopers, and an ability to communicate with both technical (developers) andnon-technical

(customers, management) people is useful. Previous softwaredevelopme nt experience can be helpful as it provides a deeper understanding of the software

development process, gives the tester an appreciation for thedevelopers' point of view, and reduce the learning curve in automated test toolprogramming. Judgment skills are

needed to assess high-risk areas of anapplication on which to focus testing efforts when time is limited. What makes a good Software QA engineer?

The same qualities a good tester has are useful for a QA engineer. Additionally,they must be able to understand the entire software development process andhow it

can fit into the business approach and goals of the organization.Comm unication skills and the ability to understand various sides of issues areimportant. In organizations in the

early stages of implementing QA processes,patience and diplomacy are especially needed. An ability to find problems as wellas to see 'what's missing' is important for

inspections and reviews. What makes a good QA or Test manager? A good QA, test, or QA/Test(combined) manager should: be familiar with the software development

process be able to maintain enthusiasm of their team and promote a positiveatmosphere, despite what is a somewhat 'negative' process (e.g., looking for or preventingproblems

) be able to promote teamwork to increase productivity be able to promote cooperation between software, test, and QA engineers have the diplomatic skills

needed to promote improvements in QA processes have the ability to withstand pressures and say 'no' to other managers whenquality is insufficient or QA processes are not

being adhered to have people judgement skills for hiring and keeping skilled personnel be able to communicate with technical and nontechnical people, engineers,managers,

and customers. be able to run meetings and keep them focused What's the role of documentation in QA? Critical. (Note that documentation can be electronic, not

necessarily paper.) QApractices should be documented such that they are repeatable. Specifications,desig ns, business rules, inspection reports, configurations, code changes, testplans,

test cases, bug reports, user manuals, etc. should all be documented.There should ideally be a system for easily finding and obtaining documents

anddetermining what documentation will have a particular piece of information.Change management for documentation should be used if possible.

What's the big deal about 'requirements'? One of the most reliable methods of insuring problems, or failure, in a complexsoftware project is to have poorly documented requirements

specifications.Requi rements are the details describing an application's externallyperceivedfunctionali ty and properties. Requirements should be clear, complete,

reasonablydetailed, cohesive, attainable, and testable. A nontestable requirement wouldbe, for example, 'userfriendly' (too subjective). A testable requirement would besomething

like 'the user must enter their previously-assigned password to accessthe application'. Determining and organizing requirements details in a useful

andefficient way can be a difficult effort; different methods are available dependingon the particular project. Many books are available that describe

variousapproaches to this task. (See the Bookstore section's 'Software RequirementsEngin eering' category for books on Software Requirements.)Care should be taken to involve ALL of a

project's significant 'customers' in therequirements process. 'Customers' could be in-house personnel or out, and couldinclude end-users, customer acceptance testers, customer contract

officers,customer management, future software maintenance engineers, salespeople,etc. Anyone who could later derail the project if their expectations aren't

metshould be included if possible.Organizatio ns vary considerably in their handling of requirements specifications.Ideall y, the requirements are spelled out in a document with

statements such as'The product shall.....'. 'Design' specifications should not be confused with'requirements'; design specifications should be traceable

back to therequirements.In some organizations requirements may end up in high level project plans,functional specification documents, in design documents,

or in other documentsat various levels of detail. No matter what they are called, some type of documentation with detailed requirements will be needed by testers in order toproperly

plan and execute tests. Without such documentation, there will be noclear-cut way to determine if a software application is performing correctly.'Agile' methods such as XP

use methods requiring close interaction andcooperation between programmers and customers/end-users to iterativelydevelop requirements. The programmer uses

'Test first' development to firstcreate automated unit testing code, which essentially embodies therequirements. What steps are needed to develop

and run software tests? The following are some of the steps to consider: Obtain requirements, functional design, and internal design specifications andother necessary

documents Obtain budget and schedule requirements Determine projectrelated personnel and their responsibilities, reportingrequiremen ts, required standards and

processes (such as release processes,change processes, etc.) Identify application's higherrisk aspects, set priorities, and determine scopeand limitations of tests

Determine test approaches and methods - unit, integration, functional, system,load, usability tests, etc. Determine test environment requirements

(hardware, software,communic ations, etc.) Determine testware requirements (record/playback tools, coverage analyzers,

test tracking, problem/bug tracking, etc.) Determine test input data requirements Identify tasks, those responsible for tasks, and labor requirements Set schedule estimates,

timelines, milestones Determine input equivalence classes, boundary value analyses, error classes Prepare test plan document and have needed reviews/approvals

Write test cases Have needed reviews/inspections/ approvals of test cases Prepare test environment and testware, obtain needed user manuals/referenced ocuments/configurat

ion guides/installation guides, set up test trackingprocesses, set up logging and archiving processes, set up or obtain test inputdata Obtain and install software releases Perform

tests Evaluate and report results Track problems/bugs and fixes Retest as needed Maintain and update test plans, test cases, test environment, and testwarethrough life cycle

Manual Testing Interview Question

s andAnsw ers
What's a 'test plan'? A software project test plan is a

document that describes the objectives, scope, approach,and focus of a software testing effort. The process of preparing a test

plan is a useful wayto think through the efforts needed to validate the acceptability of a software product. Thecompleted document will

help people outside the test group understand the 'why' and'how' of product validation. It should be thorough enough to be useful but

not so thoroughthat no one outside the test group will read it. The following are some of the items thatmight be included in a test

plan, depending on the particular project: Title Identification of software including version/release numbers Revision history of document

including authors, dates, approvals Table of Contents Purpose of document, intended audience Objective of testing effort

Software product overview Relevant related document list, such as requirements, design documents, other testplans, etc. Relevant

standards or legal requirements Traceability requirements Relevant naming conventions and identifier conventions Overall software

project organization and personnel/contactinfo/responsibiltie s Test organization and personnel/contactinfo/responsibiliti es Assumptions

and dependencies Project risk analysis Testing priorities and focus Scope and limitations of testing Test outline - a decomposition of

the test approach by test type, feature, functionality,proc ess, system, module, etc. as applicable Outline of data input equivalence

classes, boundary value analysis, error classes Test environment hardware, operating systems, other required software, dataconfigurations

, interfaces to other systems Test environment validity analysis differences between the test and productionsystem s and their impact

on test validity. Test environment setup and configuration issues Software migration processes Software CM processes Test

data setup requirements Database setup requirements Outline of systemlogging/errorlogging/other capabilities, and tools such as

screencapture software, that will be used to help describe and report bugs Discussion of any specialized software or hardware tools

that will be used by testers tohelp track the cause or source of bugs Test automation justification and overview Test tools to be used, including

versions, patches, etc. Test script/test code maintenance processes and version control Problem tracking and resolution tools and

processes Project test metrics to be used Reporting requirements and testing deliverables Software entrance and exit criteria Initial sanity

testing period and criteria Test suspension and restart criteria Personnel allocation Personnel pretraining needs Test site/location

Outside test organizations to be utilized and their purpose, responsibilties, deliverables,conta ct persons, and coordination issues Relevant

proprietary, classified, security, and licensing issues. Open issues Appendix glossary, acronyms, etc. What's a 'test case'?

 A test case is a document that describes an input, action, or event and an expectedresponse, to determine if a feature of an application is

working correctly. A test caseshould contain particulars such as test case identifier, test case name, objective, testconditions/setu p, input data

requirements, steps, and expected results. Note that the process of developing test cases can help find problems in therequirements

or design of an application, since it requires completely thinking throughthe operation of the application. For this reason, it's

useful to prepare test cases early inthe development cycle if possible. What should be done after a bug is found? The bug needs to be communicated

and assigned to developers that can fix it. After theproblem is resolved, fixes should be retested, and determinations made

regardingrequirem ents for regression testing to check that fixes didn't create problems elsewhere. If a problem-tracking system is in place, it should

encapsulate these processes. A variety of commercial problemtracking/managem ent software tools are available (see the 'Tools'section

for web resources with listings of such tools). The following are items to consider in the tracking process: Complete information such

that developers can understand the bug, get an idea of it'sseverity, and reproduce it if necessary. Bug identifier (number, ID,

etc.) Current bug status (e.g., 'Released for Retest', 'New', etc.) The application name or identifier and version The function, module,

feature, object, screen, etc. where the bug occurred Environment specifics, system, platform, relevant hardware specifics Test case

name/number/ide ntifier One-line bug description Full bug description Description of steps needed to reproduce the bug if not covered by

a test case or if thedeveloper doesn't have easy access to the test case/test script/test tool Names and/or descriptions of file/data/messages

/etc. used in test File excerpts/error messages/log file excerpts/screen shots/test tool logs that would behelpful in finding the cause of the problem

Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common) Was the bug reproducible? Tester name Test date Bug

reporting date Name of developer/group/o rganization the problem is assigned to Description of problem cause Description of fix

Code section/file/modul e/class/method that was fixed Date of fix Application version that contains the fix Tester responsible

for retest Retest date Retest results Regression testing requirements Tester responsible for regression tests Regression testing resultsA

reporting or tracking process should enable notification of appropriate personnel atvarious stages. For instance, testers need to

know when retesting is needed, developersneed to know when bugs are found and how to get the needed information, andreporting/sum

mary capabilities are needed for managers. What's a 'test plan'? A software project test plan is a document that describes the objectives, scope,

approach,and focus of a software testing effort. The process of preparing a test plan is a useful wayto think through the efforts

needed to validate the acceptability of a software product. Thecompleted document will help people outside the test group understand

the 'why' and'how' of product validation. It should be thorough enough to be useful but not so thoroughthat no one outside the

test group will read it. The following are some of the items thatmight be included in a test plan, depending on the particular project: Title

Identification of software including version/release numbers Revision history of document including authors, dates, approvals Table of

Contents Purpose of document, intended audience Objective of testing effort Software product overview Relevant related

document list, such as requirements, design documents, other testplans, etc. Relevant standards or legal requirements Traceability

requirements Relevant naming conventions and identifier conventions Overall software project organization and personnel/contact-

info/responsibiltie s Test organization and personnel/contactinfo/responsibiliti es Assumptions and dependencies Project risk analysis Testing

priorities and focus Scope and limitations of testing Test outline - a decomposition of the test approach by test type, feature,

functionality,proc ess, system, module, etc. as applicable Outline of data input equivalence classes, boundary value analysis, error classes Test

environment hardware, operating systems, other required software, dataconfigurations , interfaces to other systems Test environment

validity analysis differences between the test and productionsystem s and their impact on test validity. Test environment setup and

configuration issues Software migration processes Software CM processes Test data setup requirements Database setup

requirements Outline of systemlogging/errorlogging/other capabilities, and tools such as screencapture software, that will be used to help

describe and report bugs Discussion of any specialized software or hardware tools that will be used by testers tohelp track the cause or

source of bugs Test automation justification and overview Test tools to be used, including versions, patches, etc. Test script/test code

maintenance processes and version control Problem tracking and resolution tools and processes Project test metrics to be used Reporting

requirements and testing deliverables Software entrance and exit criteria Initial sanity testing period and criteria Test suspension and

restart criteria Personnel allocation Personnel pretraining needs Test site/location Outside test organizations to be utilized and

their purpose, responsibilties, deliverables,conta ct persons, and coordination issues Relevant proprietary, classified, security, and

licensing issues. Open issues Appendix glossary, acronyms, etc. What's a 'test case'? A test case is a document that describes an input,

action, or event and an expectedresponse, to determine if a feature of an application is working correctly. A test caseshould contain particulars

such as test case identifier, test case name, objective, testconditions/setu p, input data requirements, steps, and expected results.

Note that the process of developing test cases can help find problems in therequirements or design of an application, since it requires

completely thinking throughthe operation of the application. For this reason, it's useful to prepare test cases early

inthe development cycle if possible. What should be done after a bug is found? The bug needs to be communicated and assigned to developers that

can fix it. After theproblem is resolved, fixes should be retested, and determinations made regardingrequirem ents for regression

testing to check that fixes didn't create problems elsewhere. If a problem-tracking system is in place, it should encapsulate these processes. A

variety of commercial problemtracking/managem ent software tools are available (see the 'Tools'section for web resources with listings of

such tools). The following are items to consider in the tracking process: Complete information such that developers can understand

the bug, get an idea of it'sseverity, and reproduce it if necessary. Bug identifier (number, ID, etc.) Current bug status (e.g.,

'Released for Retest', 'New', etc.) The application name or identifier and version The function, module, feature,

object, screen, etc. where the bug occurred Environment specifics, system, platform, relevant hardware specifics Test case

name/number/ide ntifier One-line bug description Full bug description Description of steps needed to reproduce the bug if not covered by

a test case or if thedeveloper doesn't have easy access to the test case/test script/test tool Names and/or descriptions of file/data/messages

/etc. used in test File excerpts/error messages/log file excerpts/screen shots/test tool logs that would behelpful in finding the cause of the problem

Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common) Was the bug reproducible? Tester name Test date Bug

reporting date Name of developer/group/o rganization the problem is assigned to Description of problem cause Description of fix

Code section/file/modul e/class/method that was fixed Date of fix Application version that contains the fix Tester responsible

for retest Retest date Retest results Regression testing requirements Tester responsible for regression tests Regression testing resultsA

reporting or tracking process should enable notification of appropriate personnel atvarious stages. For instance, testers need to

know when retesting is needed, developersneed to know when bugs are found and how to get the needed information, andreporting/sum

mary capabilities are needed for managers.

Software Testing Interview Questions

91. Can u test a website or a web application manually without using anyautomation tool? As per my idea we can test a web

application manually without using automation but itstime consuming and might have error so to make our task easy and error free we

useautomatons tool like Qtp.As for as Manual is concerned we can test Usability, Functionality, Security testing butwhereasperfor mance is

concerned we cant do it manually accurate 92. What tools are used in Manual testing for bug tracking and reporting?

For bug tracking and reporting there are many tools likeRational clear quest.PVCSBugzi lla

93. At what stage in the SDLC testing should be started? Testing Starts from the starting sate of SDLC that is requirement stage where we

prepareSRS Or URS DOC. 94. What is mean by designing the application and coding the application? Designing and Testing are two

different phases in a software developmentproce ss(SDLC).1. Information Gathering2. Analysis3. Designing 4. Coding5.

Testing 6. Implementation and Maintenance.If u want answer in Testing terms means STLC, designing test includes preparing

TestStrategy, Test Plan and Test Case documents, and testing means executing the test casesand generating Test Reports.Designing the application as

per the requirements Designing the application is nothingbut deriving thefunctional flow , alternative flow,How many

modules that we are handling, data flow etcTwo types of designs are thereHLD:In this designing team will prepare functional architecture i.e

Functional flowLLD:In this designing team will divide the total application into modules and they will derivelogic for eachmodule

Coding:writing the course code as per the LLD to meet customer requirements 95. what is mean by client and server?

96. I. A code inspection is held for new code. II. A code inspection is held for reusedcode. III. A code inspection is held after the first compilation. IV. A

code inspectionis held after the first error-free compilation. Which of the statements above are trueof code inspections?1. I and IV 2. I, II, and IV 3. I, II, and III 4.

II and IV 5. II and III? 1. I and IV 96. What is the best way to choose automation tool? We use automation only for version wised

projects, means if the project comes up withdifferent versions. Once we write the scripts for one version, we can use these scriptswith multiple versions

with minor changes. So the main advantage of automation is:1. Saves the time.2. Saves money. 97. What is the point of reference by which

something can be measured?1. Benchmark 2. Baseline 3. Metric 4. Measure 5. Indicator Baseline

98. what is Concurrency Testing? Multi-user testing geared towards determining the effects of accessing the sameapplication

code, module or database records. Identifies and measures the level of locking, deadlocking and use of singlethreaded code and

locking semaphores. 99. When does metrics validation occur? 1. Throughout the life cycle 2. During thetest 3. After the test 4. During

requirements definition 5. After the final softwarerelease Justify your answer with simple explanation.? Throughout the life cycle - TO

identify the lag & overcome 100. The scenario is while reviewing requirement docs(SRS)if u find or feel anyrequirement is not meeting the

clients requirements whom do you report?andwhat is your action? When the System Requirement Specification does not meet the

clients requirements, itshould be intimated to the PL (who prepares the SRS and should be documented in theTest log &

analysis of data which should be discussed in the Management ReviewMeeting. The action is the SRS should undergo a revision thereby updating

SRS to matchwith CRS 101. How to choose a test automation tool? We have to choose depends upon the application

complexity & delivery time. 102. Did u come across STUBS and DRIVERS? How did u use these in u r project ? Stub : A piece of code that

simulates the activity of missing components.Drive r : A piece of code that passes test cases to another piece of code.i will give a gen example.suppos

e u have 3 modulesA B CA n B r 100%comp.and C is only 50% comp.u r under pressure to comp in a time frame what udo is u

know to build the mod C u need at least 15 daysso u build a dummy mod Cwhich will take 1/2 days This is STUB now once all the mod A B and

C(dummy) r ready..u integrate them to see how it works..This is a DRIVER 103. How to determine if a test

environment is appropriate? | 81. On what basis you are fixing up the time for project completion? Test strategy; Based on the test

strategy and testing Approach 82. How u r breaking down the project among team members? It can be depend on these following cases-1)

Number of modules2) Number of team members3) Complexity of the Project4) Time Duration of the project5) Team members

experienceetc 83. Usually customers wont give all the requirements. How will u manage & collectall the

necessary information? Sometimes customer may not produce all the requirements. At this situation Businessanalyst and project

manager will use their experience which they handles this type of projects otherwise we will go through some reference sites where we will

observe thefunctionality and they will prepare use cases and requirements.or I am agree with the above answer.If we really face

such a problem then it is better to get information from developmentteam so that we can know the exact info Or else use

Ad-hoc testing for the required job. 84. what are the Qualities needed by a software tester? A software tester must have intent of showing the product is not

working as specified.Software tester have the basic attitude of showing the presence of errors. He must haveperspective of customers i.e

he has to use the system as he is the client of the system. Hehas to strive for the quality.Or Softwa re Tester must has these qualities 1)He/she must

observe the problem from both the side say user and programmer.2)Mu st has good under standing with other team members .3)Able

to understand programmers view.4)Once start testing, do not put it remain.5)First test requirements of the user.6)Before start testing first

analysis the project like ;technology using in project, all the flow etc 85. Did you write test cases of design phase?

Yes We can write test cases at the design phaseAt the time of designing we should be ready with test cases 86. In Testing 10 cases you found 20

bugs then how will you know which bug is forwhich test case? Each Bug Will Have a Unique Bug-ID which would be related to that particular

TestCase. We also make use of the Matrix to keep track of bugs and test cases. 87. what is the path for test director,where the

test cases are stored ? c:TDcomdirTD_p rojectnameteststes t noUsually test cases are stored in Test Plan in Test director

88. what is mean by test suite? Test suit is set of test casesGroup of test cases is nothing but functional(+ve & -ve) and GUI

89. What is the diff. b/w Baseline and Traceability matrix? Baseline : The point at which some deliverable produced during the software

engineeringproces s is put under formal change control Traceability : Is used to check if some of the test cases are left out or not in Manual

andautomated testing.Baseline is nothing but a software specification or functionality that is reviewed or accepted for development.

Once the functionality is baseline, we can start developing of the functionality.Whe re as a Traceability Matrix lists all the

functionality or features and the test cases for each feature. By using the traceability matrix we can measure, when to stop testing of theproject or

application.Gener ally Traceability Matrix contains:1. UseCaseID(Functi onality/Feature).2. Description of the Feature.3. Priority for the Feature.4. TestCaseIDs for

this Feature. (Once if the mapped testcases for each Feature meetsSuccess criteria, then we can stop testing of the project)5. In which phase is the

Feature (Unit,Component, Integration,Syste m) 90. what methodologies you are following? Methodologies are considered in 2

accounts.1) There are a few methodologies like : vmodel,spiral (most common), waterfall, hybrid,prototype, etc depends on the

company.2) Depends on the clients and the requirements.No. 2 is def related to no 1Methodology means the way we are following while writing test

cases . there aredifferent ways like1. Functional Test cases2. Equivalence Partitioning Test cases3. Boundary value analysis4.

Cause Effect Graphing and Decision table 73. suppose u have raised one bug.u have posted to that concerned developer..hecant accept that is a

bug.what will u do in the next stage? If the developer wont accept our sent bug, then we show it to our team leader or we canshow it to our superior person.

so he/she will go and discuss with developer or else theywill conduct one meeting on that.or Sometimes bug not reproducible in Dev

Environment at that situation dev doesnt acceptwe will give him screen shots.If still debate occurs we raise the issue in bug triagemeeting

74. Role of Software Test Engineer in Software Company? The role of a software test engineer in company is to find

the defect. He/She should havetestto-break attitude. He/She has to test the application taking the customer into mind.He should

work hard for quality. 75. Suppose you testing Calculator application and you got problems like 1/1=2,2/2=1, 3/3=6, 4/4=1, 5/5=10. Now how

will you describe the bug title as well as givethe bug description? Bug title : Calculation ErrorsDescription: Unable to do the calculations of

this application.like the output is giving anundefined/Unstr uctured format.Here the examples : 1/1=2

Severity : CriticalPriority: High/Medium(dep ends on your Requirement to solve)Bug Title:calculator_fu nctionality_Divisi onDescription:Div

ision function is not working properly when the values are(both) sameand even. 76. Explain equivalence partitioning with an example?

When We have an requirement which has a large class of data split the large class into itssubsetsFor Ex:Sal 1000045000Here this is the large class of

data equivalence partitioning >take inputs from the belowsubclasses such asless than 10000 (invalid)between 10000 and 45000

(valid)greater than 45000 (invalid)Instead of choosing values from the large set of information split the inputs into bothvalid & negative inputs

that becomes a subset. this technique is equivalence partitioning 77. Explain traceability matrix with an example?
Manual Testing Interview Questions and Answers
Download this Document for FreePrintMobileCollectionsReport Document Report this document?

Please tell us reason(s) for reporting this document

Top of Form

af5efbe63487914 doc

Spam or junk Porn adult content Hateful or offensive If you are the copyright owner of this document and want to report it, please follow these directions to submit a copyright infringement notice. Report Cancel
Bottom of Form

This is a private document.

Info and Rating

Reads: 221 Uploaded: 12/27/2010 Category: Uncategorized. Rated:
0 5 false false 0

Copyright: Attribution Non-commercial Follow

Sumanth Kumar

Share & Embed Related Documents

PreviousNext 1.

p.

p.

p. 2.

p.

p.

p. 3.

p.

p.

p. 4.

p.

p.

p. 5.

p.

p.

p. 6.

p.

p.

p. 7.

p.

More from this user

PreviousNext 1.

88 p.

Recent Readcasters Add a Comment

Top of Form

af5efbe63487914

Submit Characters: 400

document_comme 4gen
Bottom of Form

Print this document High Quality

Open the downloaded document, and select print from the file menu (PDF reader required). Download and Print

You Must be Logged in to Download a Document

Use your Facebook login and see what your friends are reading and sharing. Other login options Login with Facebook
http://w w w .scrib 45934288 http://w w w .scrib dow nload Scribd.logged_in
Bottom of Form Top of Form

Signup
I don't have a Facebook account
Top of Form

af5efbe63487914 45934288 dow nload Scribd.logged_in

email address (required) create username (required) password (required) Send me the Scribd Newsletter, and occasional account related communications. Sign Up Privacy policy You will receive email notifications regarding your account activity. You can manage these notifications in your account settings. We promise to respect your privacy.
Bottom of Form

Why Sign up?

Discover and connect with people of similar interests. Publish your documents quickly and easily. Share your reading interests on Scribd and social sites.

Already have a Scribd account?

Top of Form

af5efbe63487914 45934288 dow nload Scribd.logged_in

email address or username password Log In Trouble logging in?

Bottom of Form

Login Successful
Now bringing you back...

 Back to Login

Reset your password

Please enter your email address below to reset your password. We will send you an email with instructions on how to continue.
Top of Form

af5efbe63487914

Email address: You need to provide a login for this account as well. Login: Submit
Bottom of Form

Upload a Document Search Documents

Top of Form

Bottom of Form

Follow Us! scribd.com/scribd twitter.com/scribd facebook.com/scribd About Press Blog Partners Scribd 101 Web Stuff Scribd Store Support FAQ Developers / API Jobs

Terms Copyright Privacy

Copyright 2011 Scribd Inc. Language: English Choose the language in which you want to experience Scribd: English Espaol Portugus (Brasil)

scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd. scribd.