Software Testing Trainning - Day5

Embed Size (px)

Citation preview

  • 8/14/2019 Software Testing Trainning - Day5

    1/18

    Client Server & Web Server, V&VClient Server & Web Server, V&VTechniques.Techniques.

    Day 5-Session 1Lavanya.M

  • 8/14/2019 Software Testing Trainning - Day5

    2/18

    Verification -

    typically means conducting reviews and meetings toevaluate documents, plans, code, requirements andspecifications

    for example, checklists, issue lists, walkthroughs, and

    inspection meetings Are we building the product RIGHT?

    Validation - typically means actual testing and takes place once

    verifications are completed Are we building the RIGHT product?

    Verification and ValidationVerification and Validation

  • 8/14/2019 Software Testing Trainning - Day5

    3/18

    Verification and ValidationVerification and Validation

    S no. Verification Validation

    1. Verification is a static testingprocedure.

    Validation is dynamic testing procedure.

    2. It involves verifying therequirements, detailed designdocuments, test plans,walkthroughs and inspections ofvarious documents producedduring the development and testingprocess.

    Validation involves actual testing of theproduct as per the testplan (unit test, integration test, systemtest and acceptance test etc).

    3. It is a preventive procedure. It is a corrective procedure.

    4. Are we building the productRIGHT?

    Are we building the RIGHT product?

    5. It involves more then two to threepersons and is a group activity.

    It involves the testers and sometimesuser.

    6. It is also called Human testing,since it involves finding the errorsby persons participating in a reviewor walk through.

    It is also called Computer testing, sinceerrors are found out by testingthe software on a computer.

  • 8/14/2019 Software Testing Trainning - Day5

    4/18

    S no. Verification Validation

    7. Verification occurs onRequirements, Design and code.

    Validation occurs only on code andthe executable application.

    8. Verification is made both in theExecutable and Non Executableforms of a work product

    Validation is done only on Executableforms of a work product.

    9. Verification finds errors early in

    the requirement & design phaseand hence reduces the cost oferrors.

    Validation finds errors only during the

    testing stage and hence cost of errorsreduced is less than Verification.

    10. An effective tool for verificationtool is a Checklist.

    Various manual and automated testtools are available for Validation.

    11. It requires cooperation andscheduling of meetings anddiscussions.

    It is to check that the product satisfiesthe requirements and is accepted bythe user.

    12. Verification tasks include:1) Planning 2) Execution

    Validation tasks include:1) Planning 2) Test ware Development3) Test Execution 4) Test ware

    Maintenance

    V and V differenceV and V difference

  • 8/14/2019 Software Testing Trainning - Day5

    5/18

    S no. Verification Validation

    13. Verification activities include: 1)Requirements Verification2) Functional design verification 3)Internal Design Verification4) Code Verification

    Validation activities include:1) Unit testing 2) Usability testing3) Function testing 4) System testing 5)Acceptance testing

    14. Verification deliverables (workproducts) are:1) Verification test plan2) Inspection report3) Verification test report

    Validation deliverables are:1) Test plan 2) Test Design Specification3) Test Case Specification 4) Test

    Procedure Specification5) Test log 6) Test incident report

    V and V differenceV and V difference

  • 8/14/2019 Software Testing Trainning - Day5

    6/18

    Client ServerClient Server

    Client/server describes the relationship between two computer programs

    in which one program, the client, makes a service request from anotherprogram, the server, which fulfills the request. Although the client/serveridea can be used by programs within a single computer, it is a moreimportant idea in a network. In a network, the client/server model providesa convenient way to interconnect programs that are distributed efficientlyacross different locations. Computer transactions using the client/servermodel are very common

    A client is defined as a requester of services and a server is defined as

    the provider of services. A single machine can be both a client and aserver depending on the software configuration.

  • 8/14/2019 Software Testing Trainning - Day5

    7/18

    Examples of Client ServerExamples of Client Server

    Generally in client server, you have to install two types

    of setup.Client Setup Giving Input and output.Server Setup Database setup.

    Example: MS SQL

    Oracle

    Win runneretc.

  • 8/14/2019 Software Testing Trainning - Day5

    8/18

    Web ServerWeb Server

    A computer that delivers ( serves up ) Web pages .Every Web server has an IP address and possibly adomain name .

    For example, if you enter the URLhttp://www.pcwebopedia.com/index.html in yourbrowser , this sends a request to the server whosedomain name is pcwebopedia.com . The server then

    fetches the page named index.html and sends it toyour browser. Any computer can be turned into aWeb server by installing server software andconnecting the machine to the Internet

  • 8/14/2019 Software Testing Trainning - Day5

    9/18

    Mainframe architectureFile sharing architecture (not a client/server architecture )Two tier architectures.Three tier architectures.

    Three tier architecture with transaction processing monitortechnology.

    Three tier with message server.Three tier with an application server.

    Three tier with an ORB architecture ( Object Request Broker).Distributed/collaborative enterprise architecture.

    Different Types ofDifferent Types ofArchitecture.Architecture.

  • 8/14/2019 Software Testing Trainning - Day5

    10/18

    Two Tire ArchitectureTwo Tire ArchitectureTwo tier architectures consist of three components distributed intwo layers: client (requester of services) and server (provider ofservices).The three components are

    User System Interface (such as session, text input, dialog, anddisplay management services)

    Processing Management (such as process development,process enactment, process monitoring, and process resourceservices)

    Database Management (such as data and file services)

    The two tier design allocates the user system interfaceexclusively to the client. It places database management on the

    server and splits the processing management between client andserver, creating two layers

  • 8/14/2019 Software Testing Trainning - Day5

    11/18

    DiagramDiagram

  • 8/14/2019 Software Testing Trainning - Day5

    12/18

    Three TireThree TireArchitecture.Architecture.

    In the three tier architecture, a middle tier was added between the usersystem interface client environment and the database management server

    environment.

    There are a variety of ways of implementing this middle tier, such astransaction processing monitors, message servers, or application servers.The middle tier can perform queuing, application execution, and database

    staging.

    For example, if the middle tier provides queuing, the client can deliver itsrequest to the middle layer and disengage because the middle tier willaccess the data and return the answer to the client. In addition the middle

    layer adds scheduling and prioritization for work in progress. The three tierclient/server architecture has been shown to improve performance forgroups with a large number of users (in the thousands) and improvesflexibility when compared to the two tier approach

  • 8/14/2019 Software Testing Trainning - Day5

    13/18

    LimitationLimitationA limitation with three tier architectures is that the

    development environment is reportedly more difficultto use than the visually-oriented development of twotier applications].

    Note: Recently, mainframes have found a new useas servers in three tier architectures

  • 8/14/2019 Software Testing Trainning - Day5

    14/18

    DiagramDiagram

  • 8/14/2019 Software Testing Trainning - Day5

    15/18

    File SharingFile SharingArchitecture.Architecture.

    The original PC networks were based on file sharing architectures, where theserver downloads files from the shared location to the desktop environment. Therequested user job is then run (including logic and data) in the desktopenvironment. File sharing architectures work if shared usage is low, updatecontention is low, and the volume of data to be transferred is low.

    In the 1990s, PC LAN (local area network) computing changed because thecapacity of the file sharing was strained as the number of online user grew (it canonly satisfy about 12 users simultaneously) and graphical user interfaces (GUIs)became popular (making mainframe and terminal displays appear out of date).PCs are now being used in client/server architectures.

  • 8/14/2019 Software Testing Trainning - Day5

    16/18

    Testing in Server.Testing in Server.For the Client/Server load testing, some common objectivesinclude:

    Measuring the length of time to complete an entire task

    Discovering which hardware/software configuration provides optimal

    performance

    Tuning database queries for optimal response

    Capturing Mean-Time-To-Failure as a measure of reliability

    Measuring system capacity to handle loads without performancedegradation

    Identifying performance bottleneck

  • 8/14/2019 Software Testing Trainning - Day5

    17/18

    ExerciseExercise1. Which of the following is the odd one out?a. white boxb. glass boxc. structurald. Functional

    2. Which of the following is a black box test design technique?a. statement testingb. equivalence partitioningc. Conditional testingd. usability testing

    3.Which of the following is NOT an integration strategy?a. Design-basedb. Big-bangc. Bottom-upd. Top-down

  • 8/14/2019 Software Testing Trainning - Day5

    18/18

    ExerciseExercise4.Which of the following is a static test?a. code inspectionb. coverage analysisc. usability assessmentd. installation test

    5. A test design technique isa. a process for selecting test casesb. a process for determining expected outputsc. a way to measure the quality of softwared. a way to describe in a test plan what has to be donee. all of the above

    6. Briefly describe about SDLC & Bug Life cycle.

    7. Tell about Types of Testing.