My Profile
Active Members
TodayLast 7 Days
more...
Awards & Gifts
Online Exams
Fresher Jobs
Our fresher job section is exclusively for fresh graduates! Find jobs for freshers in major Indian
cities including Bangalore, Chennai, Hyderabad, Pune or Kochi
Resources
Find educational articles, blogs, discussion threads and other resources.
Colleges
Find details about any college in India or search for courses.
|
Resources » Articles/Knowledge Sharing » My Interview Experience »
My Interview Experience with TechM & S1
|
Hello Everyone!
Here are few testing related questions which I could recall, were asked in S1 and TechMahindra. I could not answer all of them, but now have the answer for all. I hope it would be helpful for you.
1) Difference between Test Scenario and Test case.
Ans - Test Scenario is the high level description of the functionality of an application. And Test Case is a detailed step by
step description of how we r going to test the test Scenario. We derived testcases from test scenario. E.g. the user has
logged into an application. It is a test Scenario. In test case we need to write the steps.1) Enter the login id and
password.
2) Difference between the Progression and Regression Testing.
Ans - Progression means the process of moving ahead and the regression means the process of moving backwards. Progression
testing is the testing of new features after regression testing of previous features. It tests the only newly added features
not the entire application. In regression, it tests the modified features.
3) How can it be known when to stop testing?
Ans - This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent
environment, that complete testing can never be done. Common factors in deciding when to stop are:
1) Deadlines (release deadlines, testing deadlines, etc.)
2) Test cases completed with certain percentage passed
3) Test budget depleted
4) Coverage of code/functionality/requirements reaches a specified point
5) Bug rate falls below a certain level
6) Beta or alpha testing period ends
4) What is the 'software life cycle'?
Ans - The life cycle begins when an application is first conceived and ends when it is no longer in use. It includes aspects
such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning,
coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other aspects.
5) Difference between Web testing and Client/Server Testing?
Ans - 1) Client Server uses a binary client and the web application uses a browser -based client. Client/server application
is thick client in which all the processing is done on our desktop.
2) Web application is thin client coz all the processing is done on the server side not on our desktop. Whereas the
6) What is verification and validation?
Ans - Verification - It is done at every stage of the development and the testing.
1) Whether the requirement are correct and complete.
In design phase,
1) Whether the design is correct or not
2) It is understandable for the developer or not.
3) Does the design cover all the requirement?
In Coding Phase,
1) The coding is correct or not
2) Is it giving the right results?
In testing phase,
1) Whether the testcase is correct or not
2) Is it covering all the req. or not.
Verification is done in all phases.
Validation - It is done on the exe. file to check whether the product is working according to the req. or not.
7) On which browsers u will perform compatibility testing of your site?
Ans - 1) American Online
2) Mozilla1.71
3) IE6.0,5.5,5.0,5.1
4) Netscape 7.1
5) Safari/IE 5.2 on Mac
6) Opera
8) What are stubs and Drivers?
Ans - For the Top Down Integration approach we need stubs.
Stubs are "called functions”. In top down approach we are going to test the functionality of main funtion.And our other
functions which are getting called by main are not ready. Then we create some dummy component which is called as stubs. Then
we can check the functionality of main.
In Bottom Up Integration approach we need drivers. Drivers are "calling Functions”. In this approach we are going to test the
functionality of calling function. But if the main function is not ready then we can't test the called function. To overcome
this problem we will create dummy code which will drive the sub functions. This dummy functions are called as Drivers.
9) What comes under security testing?
Ans - 1) Is security adequate?
2) Is confidentiality/user privacy protected?
3) Do your users know when they are entering or leaving secure portions of your site?
4) Access control checking
5) Authorization checking
6) Encryption and decryption
10) What are priority and severity?
Ans - Priority - It tells us how soon it is desired to fix the bug.
Severity - It tells us about the criticality of the bug. It tells how bad the bug is.
e.g. 1) if the logo of the company is misspelled in the document then it is less severe but having highest priority.
High Priority and Low Severity:-
2) If u r having search button in your page, you have misspelled it "scarch" though it is functioning as required but until
user doesn't understand what does it mean by "scarch".It would not fulfilling the requirement. So it would definitely cm in
High
Priority to resolve and though the functionality is as required the Bug will be placed in Low severity.
High Severity and Low Priority:-
only 1 in 1000 customers will be performing those steps and the application crashes, here the severity is very high as the
application crashes, but the priority to fix this bug
is very less as this will effect only one customer that to for a wrong use case.
11) There is one application which runs on a single terminal. There is another application that works on multiple terminals.
What are the tests techniques you will use on the second application that you would not do on the first application?
Ans - 1) Concurrency Test
2) Update and Rollback
3) Response time and Server connectivity
12) Mention 4 reasons why we should test software.
Ans - 1) To find defects
2) To ensure that it meets user requirements
3) To ensure that it is fit for use
4) To reduce cost of quality by delivering defect free product
5) To achieve customer satisfaction
6) Continuously improving test process
7) Reduce risk of software failure
Thanks,
Shreshtha
|
Responses
|
| Author: Vidya 22 May 2008 | Member Level: Diamond Points : 2 | Thanks for ur information
|
|
Advertise Here
|