Question: You have tested the application and it is released. The user asks for some changes in the project and gives one week time to complete it. Out of the one week, 6 days is taken by the developer to make the changes. So you have only one day to test it. What will you do in the case in case of manual testing?
Answer: In this situation I will prefer to consult the client and request him to extend the date of release for another 1 week, for thorough testing and fix the defects that are found, so that the quality product can be released.
Because it took 6 days to complete the coding part. Only 1 day for testing is remaining. Why are we testing? To find the hidden defects. So if you start testing the major functionalities in that single day left, found any defects. Than what is the situation? We cannot release the product, because there are defects in the major functionalities. So extending the date is the best possible way in this situation. Releasing a quality product is also as important as releasing the product on time. Client will be happy if there are no serious issues with the product, though you have took extra 1 week to release the product
Question: How do you implement a new testing process in a company which must replace existing process?
Answer: A lot depends on the size of the organization and the risks involved. For large organizations with high-risk (in terms of lives or property) projects, serious management buy-in is required and a formalized QA process is necessary.
Where the risk is lower, management and organizational buy-in and QA implementation may be a slower, step-at-a-time process. QA processes should be balanced with productivity so as to keep bureaucracy from getting out of hand.
For small groups or projects, a more ad-hoc process may be appropriate, depending on the type of customers and projects. A lot will depend on team leads or managers, feedback to developers, and ensuring adequate communications among customers, managers, developers, and testers. The most value for effort will often be in (a) requirements management processes, with a goal of clear, complete, testable requirement specifications embodied in requirements or design documentation, or in ‘agile’-type environments extensive continuous coordination with end-users, (b) design inspections and code inspections, and (c) post-mortems/retrospectives.
Question: What is difference between positive and Negative testing? Which one do you prefer as tester and why?
Answer:
Positive testing — In Positive testing, we write test case according to the specifications i.e. to pass the requirement given in the specification
Negative testing — In Negative testing we write test case opposite to the specs i.e. to fail the requirement given in the specification.
e.g. - If spec says a text box should accept 12 characters then for Positive test case we will say it should accept 12 characters and if we write test case saying enter 13 characters then it’s a negative test.
Question: Why we use WinRunner mostly why don’t we use Load Runner to test applications?
Answer: By Using Load Runner We can do only performance, stress and load testing. By using win runner we can do functional, GUI, Bitmap, Data base and Data driven testing.
Load runner is costly when we compare with WinRunner.
Question: What are quality matrices?
Answer: Quality metrics is used to measure various parameters in a Software Engineering.
1) It is used to measure the size of the project and complexity of the project.
2) Measuring the productivity of the people.
3) Tracking the progress of the project.
4) Analyze the software effectiveness and taking corrective action if necessary.
There are 4 types of metrics.
1) Product Metrics
2) Productivity Metrics
3) Person Month
4) Quality Metrics
Question: How do we know which specifications are important if we have short time for testing?
Answer: By taking risk analysis specification, which part is more complex in the application and for which part end user is interacting more we have to test that part first. After that if time permits test the remaining application also
Question: Consider if there is no Test lead, No Test Manager and QA Manager. If you are the senior test engineer, you are getting pressure from the client to give the build. But you see that, there r 5 high and 5 low severity bugs. So, what you will do and how you interact with the client
Answer: As you said 5 bugs are high and 5 bugs are low severity. If there is no test lead or manager not available as a senior Testing Engineer I would concentrate on 5 high severity bugs. First I will understand them and send them to the particular development team with help of project manager. If required I will explain them the situation and about the bug severity. Meanwhile I will interact with the client behalf of my test team and I will make them understand the current status of the application.
Question: What is configuration management?
Answer: Making changes to the work product systematically is called configuration management. Mostly used popular tool is VSS (Visual Source safe). It is a version control tool.
Work product: The documents are delivered at important milestones of a project.
Important Work products:
1) Project proposal
2) Project agreement
3) Project Plan
4) QA Plan
5) Test Plan
6) SRS
7) Design Doc
Configuration management Doc
9) Maintenance manual
Question: You have completed a project and the live date is next day, you got one big problem but that problem can’t be resolved in short time and the estimate is 30 days.
Answer: We could think of any workaround which would be suitable at that point of time for the problem, and make a note in the Release notes.
In case there is no workaround, then a note should be mentioned in the release notes stating it as a known issue.
Question: You have tested the application and it is released. The user asks for some changes in the project and gives one week time to complete it. Out of the one week, 6 days is taken by the developer to make the changes. So you have only one day to test it. What will you do in the case in case of manual testing?
Answer: In that case we can test the main part of the application, we can found 80% of errors in that main functionality only, and for that only we can mainly concentrate on main functionality.
Question: How will you do regression testing if you have more number of test cases?
Answer: Prioritize the Test cases based on following things.
1) Visibility to end user.
2) Test cases for their contribution to most important Functionality of system.
3) With previous experience and similar projects Testing experience etc.
Question: In QTP is there a way to add objects to the Object Repository during runtime?
Answer: In Scripting you have to write like:
Dim V1
Set v1= description.create()
v1(”Propertyname”).value=” ” ‘Wite a propertyname here like editbox
window(”").object(”Object Name”). Method(” Method Name like v1″). value
Question: If there is game which has 20 levels an expert can only play the game up to 20 levels if i am as a normal person or tester can play the game up to 12th level then how I will test the game up to 20th level. Please guide me
Answer: In general scenario as a tester, you need to understand the requirements and functionality of the game. Access privileges must be given to a tester to test all the levels individually. After integrating all the levels, he can start from the 1st level to 20th level. If a tester plays level 1 and wins that level, he can be able to enter the next level. If he looses, he should not be able to enter the next level, and it is according to the requirement. But in this situation he can now assure to the client that he already tested each and every level individually and after integration also, it is working properly, though I have not played all 20 levels.
Question: How do you test mobile handsets?
Answer: On mobile handset we do -
1) Carrier testing.
2) Language testing
3) Handset testing
Question: What is wireless testing? How do we do it? What are the concepts a test engineer should have knowledge of? How do you classify testing of wireless products?
Answer: Wireless testing having a different approach. It’s having its standards & guidelines for application testing. As per as wireless tech. like Brew, J2me .They having there carrier specific testing Procedure including general concepts of testing like types of testing used for testing. Like functional testing, usability testing etc.
Another thing is important is it PDA application or Mobile application…by keeping this things in mind you have to test…Network availability ,Compatibility, Call, SMS interrupt issues…We have to follow carrier specific checklist & Procedure for testing..
Question: How do we test protocols in Mobile testing and how many protocols are used in Mobile application.
Answer: I just came across this URL and could not help myself to comment on this. Your question looks little vague. I mean, are you talking about network level protocols or application level protocols. Or is it related to OBEX protocol implementation in Mobile Apps. Actually the same TCP/IP concepts go in mobile apps also, but when it comes down to browsing apps/downloading apps, it is generally done via WAP gateway (Not WAP Server which generally people confuse with). WAP is a standard defined to serve as a common platform as we cannot directly hook on from normal TCP/IP network to a mobile network. But it is definitely possible to call, SMS, sending mail from any browser to a mobile device, and vice versa. So how does this happen? Also are you talking about what happens at the server end, after the gateway or before that. Also, which career network are you referring to GSM/CDMA. If I have sensed right it is “OBEX” you are referring to.
What people said