1. Tell me about yourself,
2. how do you deploy a product to client machine?
3. what is the difference between severity and priority?
4. Give example for high severity and high priority, low severity and low priority and so on?
5. Explain bug life cycle for Bugzilla using whiteboard?
6. who owns the bug at different stages since the time a defect is logged?
7. who sets the priority and severity for the bug?
8.what were your responsibilities in your previous project?
9. how would you test a server client related web product ?
10. what is domain?
12. How to set up Active directory?
13. how do you check whether the product is installed on the client machine?
14.What is Acceptance testing?
15.What is Exploratory testing??
16.What is Adhoc Testing??
17.Write few critical test cases for Login Page?
18.What may be the problem with server client connectivity problem,( Unable to transfer the files or copy the files etc..) if all the following conditions are working ( Ping , network coneections)
19.What is Test Plan??
20. What is Test cases?
21.What all type of Tests you will conduct for Client and Server based?
19.What is Test Plan??
20. What is Test cases?
21.What all type of Tests you will conduct for Client and Server based?
Exploratory testing definition:
“Exploratory Testing is a testing approach that allows you to apply your ability and skill as a tester in a powerful way.”Testers have to understand the application first by exploring the application and based on this understand they should come up with the test scenarios. After that start actual testing of application.
Key tips to remember in Exploratory testing techniques:
“Exploratory Testing is a testing approach that allows you to apply your ability and skill as a tester in a powerful way.”Testers have to understand the application first by exploring the application and based on this understand they should come up with the test scenarios. After that start actual testing of application.
Key tips to remember in Exploratory testing techniques:
- Preparation of test scenarios validates the software stability.
- Exhaustively testing of the software based on the identified requirements.
- Find out the requirements as well as functionality of the software application.
- Find out the limitation of the software application.
- Identify the scope of the project.
In this type of testing the testers have to do minimum effort for planning but maximum execution cover so that tester gets exact functionality of application. This can be helpful for tester to decide what can be next to test.During testing the tester learns about behavior of the software application, start creating test plan or test scenarios. There are different exploratory testing tools in the market. One of the Exploratory testing tool is “Session Tester” that can be used as for managing and recording Session-Based Testing. The creation of test scenarios is totally based on the experience and learning of application under test.
In this type of testing tester have freedom in testing. The finding bug is not only depends on experience of tester but also on the skill of the tester.
Many of testers are thinking of when this type of testing is comes in the picture, so here are points when we can use the exploratory testing:
When you don’t have a requirement or testing document or minimal documents.
When you want to complete your application testing in short period of time
When you have to test the application in the early stage of SDLC
Advantages
It doesn’t require preparation for testing as we don’t have documents for testing.
In this type of testing time saves due to all task are doing simultaneously like Testing, Designing test scenarios and executing test scenarios.
Tester can report many issues due to incomplete requirement or missing requirement document.
Disadvantages
Few issues cannot be catch in this type of testing.
There is review of test planning & designing of test cases/scenario while testing may cause issues.
Testers have to remember the scenario what he is executing because if any bug is found then tester should report a bug with proper steps to reproduce Difficulty to perform the exact manner especially for new found bugs.
" Exploratory Testing defines in simple ways : Exploratory testing is a type of testing in which the domain exports will perform the testing on the application to explore the functionality since they do not have the proper requirement document support...."
Acceptance Testing Definition, Analogy, Method, Tasks, Details:
DEFINITION
Acceptance Testing is a level of the software testing process where a system is tested for acceptability.
The purpose of this test is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery.
acceptance testing image
ANALOGY
During the process of manufacturing a ballpoint pen, the cap, the body, the tail and clip, the ink cartridge and the ballpoint are produced separately and unit tested separately. When two or more units are ready, they are assembled and Integration Testing is performed. When the complete pen is integrated, System Testing is performed. Once the System Testing is complete, Acceptance Testing is performed so as to confirm that the ballpoint pen is ready to be made available to the end-users.
METHOD
Usually, Black Box Testing method is used in Acceptance Testing.
Testing does not usually follow a strict procedure and is not scripted but is rather ad-hoc.
TASKS
Acceptance Test Plan
Prepare
Review
Rework
Baseline
Acceptance Test Cases/Checklist
Prepare
Review
Rework
Baseline
Acceptance Test
Perform
When is it performed?
Acceptance Testing is performed after System Testing and before making the system available for actual use.
Who performs it?
Internal Acceptance Testing (Also known as Alpha Testing) is performed by members of the organization that developed the software but who are not directly involved in the project (Development or Testing). Usually, it is the members of Product Management, Sales and/or Customer Support.
External Acceptance Testing is performed by people who are not employees of the organization that developed the software.
Customer Acceptance Testing is performed by the customers of the organization that developed the software. They are the ones who asked the organization to develop the software for them. [This is in the case of the software not being owned by the organization that developed it.]
User Acceptance Testing (Also known as Beta Testing) is performed by the end users of the software. They can be the customers themselves or the customers’ customers.
Definition by ISTQB
Acceptance testing: Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.
In this type of testing tester have freedom in testing. The finding bug is not only depends on experience of tester but also on the skill of the tester.
Many of testers are thinking of when this type of testing is comes in the picture, so here are points when we can use the exploratory testing:
When you don’t have a requirement or testing document or minimal documents.
When you want to complete your application testing in short period of time
When you have to test the application in the early stage of SDLC
Advantages
It doesn’t require preparation for testing as we don’t have documents for testing.
In this type of testing time saves due to all task are doing simultaneously like Testing, Designing test scenarios and executing test scenarios.
Tester can report many issues due to incomplete requirement or missing requirement document.
Disadvantages
Few issues cannot be catch in this type of testing.
There is review of test planning & designing of test cases/scenario while testing may cause issues.
Testers have to remember the scenario what he is executing because if any bug is found then tester should report a bug with proper steps to reproduce Difficulty to perform the exact manner especially for new found bugs.
" Exploratory Testing defines in simple ways : Exploratory testing is a type of testing in which the domain exports will perform the testing on the application to explore the functionality since they do not have the proper requirement document support...."
Acceptance Testing Definition, Analogy, Method, Tasks, Details:
DEFINITION
Acceptance Testing is a level of the software testing process where a system is tested for acceptability.
The purpose of this test is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery.
acceptance testing image
ANALOGY
During the process of manufacturing a ballpoint pen, the cap, the body, the tail and clip, the ink cartridge and the ballpoint are produced separately and unit tested separately. When two or more units are ready, they are assembled and Integration Testing is performed. When the complete pen is integrated, System Testing is performed. Once the System Testing is complete, Acceptance Testing is performed so as to confirm that the ballpoint pen is ready to be made available to the end-users.
METHOD
Usually, Black Box Testing method is used in Acceptance Testing.
Testing does not usually follow a strict procedure and is not scripted but is rather ad-hoc.
TASKS
Acceptance Test Plan
Prepare
Review
Rework
Baseline
Acceptance Test Cases/Checklist
Prepare
Review
Rework
Baseline
Acceptance Test
Perform
When is it performed?
Acceptance Testing is performed after System Testing and before making the system available for actual use.
Who performs it?
Internal Acceptance Testing (Also known as Alpha Testing) is performed by members of the organization that developed the software but who are not directly involved in the project (Development or Testing). Usually, it is the members of Product Management, Sales and/or Customer Support.
External Acceptance Testing is performed by people who are not employees of the organization that developed the software.
Customer Acceptance Testing is performed by the customers of the organization that developed the software. They are the ones who asked the organization to develop the software for them. [This is in the case of the software not being owned by the organization that developed it.]
User Acceptance Testing (Also known as Beta Testing) is performed by the end users of the software. They can be the customers themselves or the customers’ customers.
Definition by ISTQB
Acceptance testing: Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.
No comments:
Post a Comment