
- Forum
- Testing
- Software Testing
- Manual Testing Interview Questions
Manual Testing Interview Questions
This is a discussion on Manual Testing Interview Questions within the Software Testing forums, part of the Testing category; hi, I want to know answers of these questions, please answer these if u know thank you very much devi ...
-
Manual Testing Interview Questions
hi,
I want to know answers of these questions, please answer these if u know
thank you very much
devi
QA questions
Describe your QA experience (emphasis on Telecom)
What testing tools have you used? How long?
What is white box, black box?
What testing phases have you participated in?
What’s the difference between functional testing, system test, and UAT?
Have you used testing calendars? In what phase?
When would you perform regression testing?
What would you base your test cases on?
How do you make sure the results are as expected?
What’s more important: Positive or Negative testing?
How would you create test data that is as close as possible to real data?
Do you have experience with Oracle?
Have you used SQL? For what purposes?
What is your knowledge/experience with Unix?
Have you used Unix shell scripts?
Have you written WinRunner scripts?
Have you written LoadRunner scripts?
What tools did you use to log defects?
What do you think is the main challenge in testing software
What other groups did you interact with (developers, users, analysts)
Who would you rather work with?
When you realize the load you have cannot be done in the time given, how would you handle?
-
Answer for 3rd
White box testing : White box testing is a test case design method that uses the control structure of the procedural design to derive test cases.
Black box testing : Black box testing attempts to derive sets of inputs that will fully exercise all the functional requirements of a system.
-
05-16-2008, 06:57 AM #3
- Join Date
- May 2008
- Answers
- 2
When would you perform regression testing?
This depends on the requirements and the lifespan of a product, but there are many other factors that influence whether regression testing needs to be done.
An example would be a product that is at certain stage in it's life cycle, and there is a requirement for a new version to replace the old version.
In theory the ideal scenario would be that the new version of the software fully supports the legacy functions of the previous version and is able to add new functionality to the product without compromising the functional integrity of the overall product.
With that in mind, this is where regression testing would be done, as you would now want to ascertain whether the new version of the product does not add new defects into the system.
Hope this helps.
-
WHITE BOX TESTING: it is nothing but testing the structural and logic behind the software. We need to write test cases satisfying all the paths and loops in the module and check whether the logic is satisfied. It is logic driven testing.
BLACK BOX TESTING: It is jus checking the software for the necessary results by providing different input. It is requirement driving testing.
REGRESSION TESTING: It is testing the software in every version or after fixing the bug or enhancement, to check whether any new errors have been inculcated in the software because of the new build.
-
08-26-2008, 03:05 AM #5
Hi Devi...
Describe your QA experience (emphasis on Telecom)
Only QA can Prevent the software from Defects and moniter whether the software meet the requirement and by Testing only we can find defect in the software. so if u have QA experience u can tell that.
What testing tools have you used? How long?
If u r using any tool u can tell that.. other wise tell no.. in manual testing we wont use any tools. except test directors. u can tell about test director (or QC).
What is white box, black box?
White Box:- White box testing is based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths and conditions.
Black Box:- Black box testing is functional testing, not based on any knowledge of internal software design or code. Black box testing are based on requirements and functionality.
What testing phases have you participated in?
Functional Testing, Regression Testing. or u can say System Testing. System Integration Testing.
What’s the difference between functional testing, system test, and UAT?
Functional Testing:- testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions. this is a black box testing.
System Testing:- System testing is black box testing, performed by the Test Team, and at the start of the system testing the complete system is configured in a controlled environment. The purpose of system testing is to validate an application's accuracy and completeness in performing the functions as designed. System testing simulates real life scenarios that occur in a "simulated real life" test environment and test all functions of the system that are required in real life. System testing is deemed complete when actual results and expected results are either in line or differences are explainable or acceptable, based on client input.
UAT:- Acceptance testing is black box testing that gives the client/ customer/ project manager the opportunity to verify the system functionality and usability prior to the system being released to production. The acceptance test is the responsibility of the client/customer or project manager, however, it is conducted with the full support of the project team. The test team also works with the client/customer/project manager to develop the acceptance criteria.
When would you perform regression testing?
Regression testing is verifing that previously passed tests are still OK after any change to the software or the environment, usually to verify that a change in one area doesn't affect other or unrelated areas.
What would you base your test cases on?
A test case is a document that describes an input, action, or event and its expected result, in order to determine if a feature of an application is working correctly. A test case should contain particulars such as a...
· Test case identifier;
· Test case name;
· Objective;
· Test conditions/setup;
· Input data requirements/steps, and
· Expected results.
Test cases will be prepared by the tester based on BRD & FS.
How do you make sure the results are as expected?
In Functional or System testing we will test with real time data. and realtime scenarious with client approved test cases, so that we will know what is correct result.
What’s more important: Positive or Negative testing?
Both are important, but most of the test cases will be returned for Positive, for some applications Negetive cases also important.
Have you used SQL? For what purposes?
the answer is up to u.
What is your knowledge/experience with Unix?
Have you used Unix shell scripts?
Have you written WinRunner scripts?
Have you written LoadRunner scripts?
What tools did you use to log defects?
u can say Test Director or Quality Centeror excel sheet.
What other groups did you interact with (developers, users, analysts)
Who would you rather work with?
Analysts
When you realize the load you have cannot be done in the time given, how would you handle?
Use risk analysis to determine where testing should be focused.based on some consideration we can come up with task of completing complete testing.some are
Which functionality is most important to the project's intended purpose?
Which functionality is most visible to the user?
Which functionality has the largest safety impact?
Which functionality has the largest financial impact on users?
Which aspects of the application are most important to the customer?
Which aspects of the application can be tested early in the development cycle?
Which parts of the code are most complex, and thus most subject to errors?
Which parts of the application were developed in rush or panic mode?
Which aspects of similar/related previous projects caused problems?
Which aspects of similar/related previous projects had large maintenance expenses?
Which parts of the requirements and design are unclear or poorly thought out?
What do the developers think are the highest-risk aspects of the application?
What kinds of problems would cause the worst publicity?
What kinds of problems would cause the most customer service complaints?
What kinds of tests could easily cover multiple functionalities?
Which tests will have the best high-risk-coverage to time-required ratio?
I am giving this answers with my experience. if u feel anything wrong. please excuse..
bye Devi
-
09-04-2008, 07:53 AM #6
- Join Date
- Jan 2007
- Answers
- 1
Ans:7 Whenever any new changes are done or bugs are fixed by developers we have to perform regression testing in order to see that no additional bugs have been introduced due to changes.
Last edited by himanshu_meb; 09-04-2008 at 07:55 AM. Reason: Missing Details
-
Hi,
I agreed with you. Any way, your ideal make me thinking about some thing for my project.
Please try to keep posting. Tks and best regards
-
hi
3)Whitebox testing:
White box testing is performed based on the knowledge of how the system is implemented. White box testing includes analyzing data flow, control flow, information flow, coding practices, and exception and error handling within the system, to test the intended and unintended software behavior. White box testing can be performed to validate whether code implementation follows intended design, to validate implemented security functionality, and to uncover exploitable vulnerabilities.
Blackbox testing:
Black-box testing is a method of testing software that tests the functionality of an application as opposed to its internal structures or workings (see white box testing). Specific knowledge of the application's code/internal structure and programming knowledge in general is not required. Test cases are built around specifications and requirements, i.e., what the application is supposed to do. It uses external descriptions of the software, including specifications, requirements, and design to derive test cases.
4) System testing,functional testing, user acceptance testing
5)Functional testing:
Functional testing is testing the functionality of the software whether the software developed behaves in intended purpose or not.
System testing:
System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements and it also includes non functional testing like performance and load testing.
User Acceptance Testing is a key feature of projects to implement new systems or processes.
It is the formal means by which we ensure that the new system or process does actually meet the essential user requirements.
-
Hi
I found that a member asked same question in this forum some months ago.
Pls use search box to find this questions with comments
-
Hi,
Thanks very much for this comment. It help me to think about my ideals.
Tks again and pls keep posting.
-
Sponsored Ads

Reply With Quote






