If you are going to attend an interview in Manual Testing, then you have to prepare for the following basic questions which were asked in many interviews.
1) Prepare about you and your professional experience. It will be within 3 to 5 minutes.
2) Prepare something about your company details
3) Your Roles and Responsibilities in your company
4) Prepare about your current project. You have to tell the Project title, Client of the project, Short Description about the project, how many modules are there in the project and which part you have involved in the project.
5) Your Daily Regular activities after entering and leaving from office?
6) Types of testing u have done in your experience?
7) What are the challenges situations you have faced?
8) What are Severity and priority and some examples?
9) What are all the achievements you made in your company in your role?
10) What are all the challenging defects you found?
11) What will you do to reproduce issues, if the developer says that he can’t able to reproduce?
12) How will you Communication within your team and stake holders?
13) What is the Difference between client server applications and Web Applications?
14) What is SDLC and explain about it?
15) What is STLC and explain about it?
16) Testing process you follow in your company?
17) What is Bug life cycle and explain about it?
18) Test case preparation and sample test cases?
19) What is Requirement traceability matrix and how will you do it in your company?
20) What is Defect traceability matrix?
21) How does a web applications works?
22) What is V- Model and explain about it?
23) What is the Difference between waterfall model and V MODEL?
24) What are all the Testing Techniques?
25) What is Boundary Value analysis and Equivalence partitioning and give examples?
If you people have more questions that will be asked in interviews, kindly add it in the comments section.
Wednesday, June 24, 2009
Severity and Priority of Defects
Generally we have to set the Severity and Priority level for a Defect. Severity level will be set by the Testing Team and the Priority level will be set by the Development Team.
Severity means how much severe is the particular defect in the application (i.e.) how it affects the functionality of the application
Priority means the importance and urgency to fix the defect by the developers (i.e.) which defect should be fixed first and which should be fixed in later versions.
There and some levels in severity and priority, they are as follows….
Severity levels:
Trivial
Minor
Major
Critical
Block
Priority Levels:
Low
Medium
High
Urgent
Immediate
The Severity and Priority levels must vary depends upon the company and the defect tracking tool used by the company.
Some Examples for the priority levels….
Low Priority: Spelling mistakes, grammatical errors, Textual Errors, Orphan pages, broken links, GUI errors,
High Priority: Wrong Functionality, Applications Crashes, Errors
If you have any feed backs for this post, kindly drop it in the comments section.
Severity means how much severe is the particular defect in the application (i.e.) how it affects the functionality of the application
Priority means the importance and urgency to fix the defect by the developers (i.e.) which defect should be fixed first and which should be fixed in later versions.
There and some levels in severity and priority, they are as follows….
Severity levels:
Trivial
Minor
Major
Critical
Block
Priority Levels:
Low
Medium
High
Urgent
Immediate
The Severity and Priority levels must vary depends upon the company and the defect tracking tool used by the company.
Some Examples for the priority levels….
Low Priority: Spelling mistakes, grammatical errors, Textual Errors, Orphan pages, broken links, GUI errors,
High Priority: Wrong Functionality, Applications Crashes, Errors
If you have any feed backs for this post, kindly drop it in the comments section.
Sunday, June 14, 2009
Details to be given while posting a Defect
I know that all the experienced Testers must have knowledge on what are all the details that should be given to a developer while posting a defect. But I am writing this article for fresh testers. Anyway experienced testers, write down your comments, feed backs and valuable points which can be added from your experience. It will be more helpful for the fresh peoples who are reading this article.
1) Category of the defect
2) Defect Reproducibility
3) Severity of the defect
4) Version of the product/project
5) OS Version
6) Environment Details
7) Summary of the defect
8) Description
9) Steps to Reproduce
10) Additional Information
11) Login Details
12) Test Data
13) Actual Result
14) Expected Result
15) Screen shots for proof
16) Videos if any for reproduce
1) Category of the defect
2) Defect Reproducibility
3) Severity of the defect
4) Version of the product/project
5) OS Version
6) Environment Details
7) Summary of the defect
8) Description
9) Steps to Reproduce
10) Additional Information
11) Login Details
12) Test Data
13) Actual Result
14) Expected Result
15) Screen shots for proof
16) Videos if any for reproduce
Wednesday, June 10, 2009
Roles and Responsibilities of a "Software Testing Engineer"
Generally Roles and Responsibilities of a Testing Engineer may vary, depending upon the working company. But here we are going to discuss about the general and important roles and responsibilities of a Testing Engineer.
1) Analyzing the Requirements from the client
2) Participating in preparing Test Plans
3) Preparing Test Scenarios
4) Preparing Test Cases for module, integration and system testing
5) Preparing Test Data’s for the test cases
6) Preparing Test Environment to execute the test cases
7) Analyzing the Test Cases prepared by other team members
8) Executing the Test Cases
9) Defect Tracking
10) Giving mandatory information of a defect to developers in order to fix it
11) Preparing Summary Reports
12) Preparing Lesson Learnt documents from the previous project testing experience
13) Preparing Suggestion Documents to improve the quality of the application
14) Communication with the Test Lead / Test Manager
15) Conducting Review Meetings within the Team
These are the Roles and Responsibilities of a Testing Engineer which is based upon my knowledge. If you know more about this kindly write it down in the comments section.
Your Feed backs are welcome!
1) Analyzing the Requirements from the client
2) Participating in preparing Test Plans
3) Preparing Test Scenarios
4) Preparing Test Cases for module, integration and system testing
5) Preparing Test Data’s for the test cases
6) Preparing Test Environment to execute the test cases
7) Analyzing the Test Cases prepared by other team members
8) Executing the Test Cases
9) Defect Tracking
10) Giving mandatory information of a defect to developers in order to fix it
11) Preparing Summary Reports
12) Preparing Lesson Learnt documents from the previous project testing experience
13) Preparing Suggestion Documents to improve the quality of the application
14) Communication with the Test Lead / Test Manager
15) Conducting Review Meetings within the Team
These are the Roles and Responsibilities of a Testing Engineer which is based upon my knowledge. If you know more about this kindly write it down in the comments section.
Your Feed backs are welcome!
Subscribe to:
Posts (Atom)