Testing Inteview Questions

Testing Inteview Questions-BFSI Domain+ Manual Testing Concepts  for 4-6 years experience.
This List includes Test lead experience questions as well. (answers for all below questions will be updated soon), the questions are in no particular format. The questions below are for various companies personally attended by me (CTS, E&Y, Deutsche bank, CGI, HCL, Polaris).The answers for few questions available in the blog are posted here after discussion with various collegues and friends in the testing and BFSI field. If you the reader of this blog has some better answers for these questions please feel free to provide it as comments so that it can be incorporated with the answers available which will benefit all of us who are in need of it.
---Prajna Shetty
  • What is investment banking?
  • How do you test reports?

  • If you have 10 requirements and 10 TC to cover the requirement, is you testing complete?

  • What is different type of securities?

  • What is a hot fix?

  • What are a stock /Share?

  • Do you do system integration testing? Why do you call it system integration?

  • What is retail banking?

  • What is the difference between a saving account and a checking account?

  • If there is new requirement coming in between a release and the client expects that even that goes as a part of the release along with the other requirements then how will you incorporate that in the release within the given schedule?

  • Trade life cycle?

  • What is an investment bank

  • What are derivatives

  • What are options

  • What are stocks/Securities

  • How is a price of an IPO decided?

  • Types of securities?

  • To do root cause analysis, what procedure do you follow?

  • In a team 2 member having same experience and same performance have conflicts in meetings which is affecting your delivery, how do you resolve this issue?
    1. Have one on one and find out what issues they have with their counter parts and explain to them that each individual’s contribution works for the success of the project.

    2. Monitor to see if the issues are resolved after your discussion, if situation hasn’t still changed give them a warning.

    3. Also can try giving them different responsibilities within the project.

    4. If there is still no improvement then escalate it your manager to take necessary steps.
  • In a team you have a fresher and an experienced person, how will you go about allocating work?
    1. Fresher’s: we will give UI test cases and module level test cases for execution and TC writing

    2. Experienced: functionality, integration, end to end test cases for execution and TC writing
  • You have 5 days for TC execution, on the fourth day you realize that one of the team members have been executing the TC‘s wrongly? How would you go about resolving this issue?
    1. Sit with him and try to identify where he went wrong, explain to him the correct method/steps for testing.

    2. As only one day remaining for delivery ask him to test the UI and the critical functionalities first based on the business criticality

    3. Or ask other team member to help in completing the execution of the TCs if they are available.

    4. Or if resources are not available in your report mention all the crucial functionalities that were tested.
  • If 4 out of 10 team members take unplanned Leave just one day before delivery what will you do?
    1. First call all of them and find out why they are on leave, if genuine can’t do anything else ask them if they can come to office for some time or can they work from home, or ask the existing team members to work for some extra time and give them comp offs at later point in time. Also check if you can get some extra resources for 1 or 2 days.
  • During execution a new requirement comes in, will you accept it? If you accept what you will do?

  • During execution a new requirement comes in which has to go in the particular release and also the time lines are fixed? In this situation how will you go about testing?

  • What are you positive point, negative points

  • Have you worked on Automation, what tool would you use if you were to work on automation, what you know of QTP?

  • Please tell me about yourself

  • How do you export data from Excel to QC

  • Please explain the details of a test plan

  • Requirement analysis issues how do you track? Is Issue tracker a tool? What will be the columns in the issue tracker?

  • If a member in your team has missed out 10 defects which are quite visible and as per the requirements, how will you tackle the situation?

  • What was a challenging issue you have faced in your project?

  • If a member from your team is on leave and you need to complete his work also what you will do as a module lead?

  • Tell us a Few important qualities that a tester should have
  • 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.

  • Tact and diplomacy are useful in maintaining a cooperative relationship with developers,

  • An ability to communicate with both technical (developers) and non-technical (customers, management) people is useful.

  • Previous software development experience can be helpful as it provides a deeper understanding of the software development process, gives the tester an appreciation for the developers’ point of view, and reduce the learning curve in automated test tool programming.

  • Judgment skills are needed to assess high-risk areas of an application on which to focus testing efforts when time is limited.
    • Tell me of a test case that you have written that you are really proud of

    • What is integration testing, Stubs, Driver – detailed knowledge expected

      • We do integration testing because a set of modules that work fine individually rarely works together correctly the first time. There are a variety of reasons:
        1. Differences in the understanding of business requirements between multiple developers cause them to assume different things should happen for the same test cases.

        2. Fields are defined differently. For instance, one module assumes a field can hold 10 characters, while another module is programmed to hold 11.

        3. There are different assumptions in field content. For example, one program expects a phone number to be 10 digits. Another expects the phone number to include the dashes.

        4. The modules still have errors that were not uncovered in unit testing. Integration testing may add new test cases, some of which may have been difficult to generate during unit testing, that result in additional errors being uncovered.

        5. In this phase of testing, individual modules are combined and tested as a group.

        6. Integration Testing is carried out by Testers. Data transfer between the modules is tested thoroughly.

        7. Consider this Integration Testing Scenario. Customer is currently in Current Balance Module. His balance is 1000. He navigates to the Transfer Module. And transfers 500 to a 3rd part account

        8. Customer navigates back to the Current Balance Module & now his latest balance should be 500.

        9. The Modules in the project are assigned to 5 different developers to reduce coding time

        10. Coder 2 is ready with Current Balance module. Coder 5 is not ready with Transfer module required to test your integration scenario. What do you do in such a situation?

        11. On approach is to use Big - Bang Integration Testing - where you wait for all modules to be developed before you begin integration testing. The major disadvantage is that it increases project execution time, since testers will be sitting idle unless all modules are developed .Also it becomes difficult to trace the root cause of defects.

        12. Alternatively, you can use Incremental approach were modules are checked for integration as and when they are available.

        13. Consider that the Transfer module is yet to be developed but Current Balance module is ready .You will create a Stub which will accept and give back data to the current balance module.

        14. Note that, this is not a complete implementation of the Transfer module which will have lots of check like 3rd party account # entered is correct, amount to transfer should not be more than amount to available in account and so on. But it will just simulate the data transfer that takes place between the two modules to facilitate testing

        15. On the contrary, if transfer module is ready  but current balance module is not  developed you will create a Driver to stimulate data transfer between the modules

        16. To increase the effectiveness of the integration testing you may use -

        17. Top to down approach where higher level modules are tested first .This technique will require creation of stubs

        18. Bottom Up approach -where lower level modules are tested first. This technique will require creation of drivers

        19. Other approaches would be functional increment & Sandwich - which is combination of top to down and bottom to up.

        20. The choice of approach chosen depends on the system architecture and location of high risk modules.

        21. Stub means a Dummy model of a particular module.
          Suppose we have to test the interface between 2 modules A and B and we have developed only module A while Module B is yet in development stage.
          So in such case we cannot test module A but, if we prepare a dummy module, having similar features like B then using that we can test module A.
          Our main aim in this is to test Module A & not Module B so that we can save time otherwise we have to wait till the module B is actually developed.
          Hence this dummy module B is called as Stub.
          Now module B cannot send/receive data from module A directly/automatically so, in such case we have to transfer data from one module to another module by some external features. This external feature used is called Driver.
      • You have 3members in your team-high medium and low performer, how will you manage your deliverable in this case?
      • Let’s take for ex: Planned for day 30 TC execution
      H Completes 12 TCs per day
      M Completes 8 TCs per day
      L Completes 4 TCs per day
      In this case I will assign
      H 12+1
      M 8+3
      L 4+2
      • Explanation for this assignment is

      • Requirements are in the form of an excel sheet, randomly changing how will you go about testing the same?
      • Have a requirements walk thru and send all your clarifications to the respective team meanwhile, assuming the base requirement will not change we can start TC design for the base requirement and wait to write TCs for the requirements around the base requirement for some more time till we receive all the clarification and till to some extent the requirements have freezed, in this way there will be proper use of available time and when there will be more clarity in requirements there will be minimum rework on the already written TCs.
        :
        as the high performer is already completing 12 so assign to him one more so that he is not over burdened. 3 to the medium performer and 2 top the low performer as already he is slow so max he could push to 2more.
      • There is a high severity defect that the team has found just one day before the release, how are you going to manage this as a team lead?
      • Accept that it is a mistake from your side and at priority log it and ask the dev team to fix it, if they say they can’t fix it discuss it with the project manager about how serious the defect is to the go live and what is the reason for them saying a no to the fix, if still they think it can’t be fixed then ask your manager to discuss it with the higher management and the stake holders and take a decision on will it be fixed for the release or can it go as a patch in the coming week and if they decide to fix it immediately then the some of the test team members might have to stay late and test it for the fix and later may be take a comp off. If option available. Once the release is completed then you will need to do a root cause analysis as to how the defect was missed and what precautions you can take going further.
      • 9balls all identical out of which one weighs more, 2chances, weighing machine provided, how will you find out that which ball weighs more.
      • Put 4balls in one side and 4balls in other of the weighing machine, now if you see a balance on both side then the ball that is left out is the heavier ball.
      • One paper, 5balls, how will you place them equidistant from each other?

      • Security testing -- authenticated/unauthenticated user login box functionality

      • A client wants to move from the client-server to web based application what kind of testing will you need to do in this case.

      • You have 2 text boxes and a go button, when you enter the employee id in one box the other box should display the employee name on clicking the go button. If no data is enter in the first box on clicking go an error message should be displayed at the top of the screen .please write all the possible test cases for this scenario.

      • You have an ATM machine for a bank ex. ICICI and it allows user of other banks to also with draw money, after some time the bank dismisses this option of clients from other banks, please write test cases for both scenarios.

      • What is agile model, what is the difference between agile and water fall model.

      • What are equities?
      

      No comments:

      Post a Comment