Case

 

Mphasis-Chennai/Pune 

1+ 

Manual Testing

50 positions

 T. Shiva Shankar : B.Tech: Mechanical 2020 

  Mail 1: Pls send defect details with proof/Attachement?

Ans: Please find bug details below 

 To: Dev@accenture.com

 CC:  

 Sbiject: Bug information

          Bug Id: Bug01

          Bug Title: Login is not working

          Bug Description: When we enter Login valid details application

                 is throwing error message

         Expected Result: Home page must be displayed

         Actual Result: Home page is not displayed

 Pls fix this defect asap 

Thanks and Regrards,

Ramana Bhupathi

Test Engineer

 Accenture       

Reply: I did not givem attachment , Sorry 

                  

         I have clicked on send button too quickly without attachment,

          Pls find attachement here 

     My Aplology, Pls find attachment now 

----------------------------------------------------------

11:40 to 01:00 : Software Testing

Key Chapters of Manual Testing -30 days 

Chapter 1: Testing Basics-Ramana

Chapter 2: Testing Life Cycle-STLC-Harish

Chapter 3: Development Life Cycle/Agile-SDLC-Annapurna

Chapter 4: JIRA-Ramana

Chapter 5: Project-Afternoon

Testing Basics

Topic 1: Software Testing Introduction

  What is Software Testing?

  Software Testing is a process which helps to deliver quality Software to

    customers 

  Why we need Software Testing?

   1. Software Testing improves Quality

   2. Software Testing gives positive feedback on application from          customers

   3. Software Testing increases number of transactions/revenue

   4. To avoid legal issues

   5. To avoid Re-work 

   6. To increase brand value

  What happens if we deliver Software without Testing?

       1. End users may give negative feedback 

       2. End users may not use your application

       3. Financial loss 

       4. Legal issues  

       5. Unnessary re-work

       6. Brand value will be affected 

Software Testing can be perfomed using 2 methodolgoies

Testing Methdologies

1. Black Box Testing

   

  Testing any Software by giving inputs using external interface 

   without accessing internal program structure/Logic/Code

 

2. White Box Testing

    

  Testing any Software by giving inputs using program level/

   Internal Strucure/Logic written  by developer 

   

3. White Box testing + Black Box testing=  Grey Box testing

  Test Engineers who has experience in Grey Box testers -SDET 

    SDET: Software Development Engineer in Test 

Software Testing help us answers questions like

• Does Software really work as expected?

• Does Software meet the users’ requirements?

• Is it what the users expect?

• Do the users like it?

• Is it compatible with the other systems, as desired?

• How does it perform?

• Is it ready for release?

Black Box Testing:

Testing the behavior of the application for the desired functionalities against the requirements without focusing the internal details of the system is called Black box Testing

It is usually performed by an independent testing team or the end users of the application

The application is tested with relevant inputs and is tested to validate if the system behaves as desired

This can be used to test both Functional and Non-functional requirements

External descriptions of the software like SRS (Software Requirements Specification), Software Design Documents are used to derive the test cases.

White Box Testing

White Box testing tests the structure of the software or software component. It checks what happens inside the software code step by step. Also Known as Clear box testing, glass box testing, or structural testing. 

It requires knowledge of internal code structure and good programming skills. It tests paths within a unit and also flow between units during integration of units

Grey Box : White Box and Black Box

Difference between Black Box & White Box Testing 

White box testing is concerned only with testing the software product; it cannot guarantee that the complete specification has been implemented. Black box testing is concerned only with testing the specification; it cannot guarantee that all parts of the implementation have been tested. 

Thus Black box testing is testing against the specification and will discover faults of omission, indicating that part of the specification has not been fulfilled. 

White box testing is testing against the implementation and will discover faults of commission, indicating that part of the implementation is faulty.

 In order to fully test a software product both black and white box testing are required. 

White box testing is much more expensive than black box testing. It requires the source code to be produced before the tests can be planned and is much more laborious in the determination of suitable input data and the determination if the software is or is not correct. 

The advice given is to start test planning with a black box test approach as soon as the specification is available. White box planning should commence as soon as all black box tests have been successfully passed, with the production of flow graphs and determination of paths. The paths should then be checked against the black box test plan and any additional required test runs determined and applied

 

Testing Technqiues:

 1. Static Testing(Verification)

 2. Dynamic Testing(Validation) 

IQ: Explain differences between Verification and Validation?

Step 1: Document Requirements-Requirements Gathering 

           A. 3 floors house -G+1+2 

           B. 1floor as swimming pool: Ground floor 

           C. NE Facing : 

           D. 300 Sft Pooja room

           E. Latest Roof type

Step 2: Verification of house requirements 

               or

         Review of house requirements

             or 

          Inspection of House requirements

           or

         Static Testing of house 

             

Step 3: Design Development

Step 4: Verification of Design 

       Is design created as per Requirements or not 

     Design review

     Design verification

    Design Static Testing

Prevent erros in design before these erroes become bug in construction

Step 5: Verification of code to prevent Bugs 

---------------------------------------------------------------------

What are the Verification Activities?

  1. Requirement Review-Preventing mistakes 

  2. Design Review -Preventing errors

  3. Code Review-Preventing Bugs 

What are the Validation Activities?

  1. AUT/SUT Validated by Developer -Unit Testing and Integration testing

          To finding and fixing defects 

  2. AUT/SUT Validated by Test Engineers -System testing/SIT testing

  3. AUT/SUT Validated by end users/customers-

            User Acceptance Testing-UAT Testing 

   Validation or Dynamic testing objective is finding and fixing defects

   before we release application to live environment/Production         enviornment 

 Prevention vs Detection 

 Verification vs Validation

 Static Testing vs Dynamic Testing

 Review vs Execution

Now we have release to live--In Live if it is not working 

we call it as Failure 1, Failure 2, Failure 2         

      

Testing= Verification and Validation 

Test Engineer is also called 

 " Independent Verification and Validation engineer"

1. Verification starts before code development from the beginning of the project whereas Validation starts after code compilation.

2. Verification objective is prevention of mistakes, errors, bugs entering to software Validation objective is finding defects through execution of Software.

3. Verification activities are Requirement review, design review,

 Code review whereas validation activities are Unit testing, Integration testing, System testing, User Acceptance Testing (UAT testing)

4. Verification is proactive testing for prevention whereas validation is reactive testing for detection of the defects.

5. Testing must starts before code development with verification activities once code is ready we do validation to find defects. 

Day 1: Sep 11:

IQ 1: Explain What is Software Testing/Why Software Testing imp?

IQ 2: Explain differences between WhiteBox Testing and Black Box Testing?

IQ 3: Explain differences between Verification and Validation?