What were you responsible to test in your previous company?
This is homework for you. Actually, this question is a test of the knowledge of your own resume. You must know your real or fake resume as a bible. Practice in front of mirror or ask you
Understanding the Functional, Specification and Design documents
Preparing the Requirement Traceability matrix and Test Plan
Test Case Preparation: Main goal is to cover each and every requirement, test cases are prepared according to the Test case standards (means Font size- Arial10, the name of the test case should be short and descriptive, without spelling and grammar mistakes etc), every requirement should have at least one test case, test cases must be prepared for all valid, invalid, expected and unexpected scenario’s, should be prepared based on the Test case template (Test case Id, Test case name, precondition, description, steps, input, Expected result, actual output, status(pass/fail), designer, date and time, application name, module name, version, Remarks)
Test Case Execution: Executing the Test case for particular scenario to decide the variation between the Expected Result and actual output. And to decide whether the given input is producing the expected output. And to analyze the application as per the requirement
Analyzing the Test Results: Analyze the results to find out is there any difference between actual and expected result. To find out the bugs. To check whether all the customer requirements are satisfied
Report the bugs and Log the bugs in the Defect Tracker: Usually Test Director,Sanity Testing: Test the application to decide whether it is ready for testing, whether the major functionalities are working or not, it is the initial testing
Retesting: Testing the application or module to check whether the reported bug is solved/ rectified or not
Regression Testing: Testing the application whether the major bug is solved and to check whether any new bugs are introduced
Functional Testing: Testing the application to check whether all the functional requirements are satisfied or testing the application according to the functionality
Bug report generation: Analyze the test results, findout the bugs, log them in the Defect Tracker, generate the report
Issue raising and resolving: while understanding the application, is at all any doubts, raise them and conduct discussions with the higher authority or team members and get them resolved
RE: What were you responsible to test in your previous...
I involved in Manual Testing part :
The following are my responsibilities:
Understanding the Functional Specification and Design documents
Preparing the Requirement Traceability matrix and Test Plan
Test Case Preparation: Main goal is to cover each and every requirement test cases are prepared according to the Test case standards (means Font size- Arial10 the name of the test case should be short and descriptive without spelling and grammar mistakes etc) every requirement should have at least one test case test cases must be prepared for all valid invalid expected and unexpected scenario s should be prepared based on the Test case template (Test case Id Test case name precondition description steps input Expected result actual output status(pass/fail) designer date and time application name module name version Remarks)
Test Case Execution: Executing the Test case for particular scenario to decide the variation between the Expected Result and actual output. And to decide whether the given input is producing the expected output. And to analyze the application as per the requirement
Analyzing the Test Results: Analyze the results to find out is there any difference between actual and expected result. To find out the bugs. To check whether all the customer requirements are satisfied
Report the bugs and Log the bugs in the Defect Tracker: Usually Test Director Sanity Testing: Test the application to decide whether it is ready for testing whether the major functionalities are working or not it is the initial testing
Retesting: Testing the application or module to check whether the reported bug is solved/ rectified or not
Regression Testing: Testing the application whether the major bug is solved and to check whether any new bugs are introduced
Functional Testing: Testing the application to check whether all the functional requirements are satisfied or testing the application according to the functionality
Bug report generation: Analyze the test results findout the bugs log them in the Defect Tracker generate the report
Issue raising and resolving: while understanding the application is at all any doubts raise them and conduct discussions with the higher authority or team members and get them resolved
2 
0