|
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
|