面试题

JOBSDB_joyce

1. Working Experience:

1.1. Introduce yourself and your projects

1.2. What you are doing best for your previous projects

1.3. What you like being a tester or SDET

1.4. What's your big challenge for this position

1.5. What are the best bugs you have every found

1.6. Have you ever worked in the offshore/onshore model before

1.7. How do you communicate with your onsite partners

2. Testing Knowledge

2.1. Difference between System testing and integration test

Integration Testing: Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.
System Testing: Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

2.2. Difference between black box testing and white box test

Black Box testing: we test the functionaliy of the application throughly with the help of requirements. here we do not concern about the internal logic of the code. here we check the system by giving the proper input whether it gives proper output or not. this work done by the testers.
White Box testing: we more concern about internal logic of the program i.e; here we check module interface local datastructures logical conditions on their true and false side loops etc; designated and executed by the developers/SDET.

2.3. Difference between performance, load, and stress testing

Performance testing: Performance testing is used to show that after testing there is no defect in the system or application. Load testing and stress testing are the parts of performance testing.
Load Testing: Load testing is used to test the application under a range of loads in order to determine at what point the system's response time degrades or fails.
For example,If an application is supports 500 users then test whether it supports the no of users as specified.
Stress Testing: This testing is used to push the system beyond the limits of its specified requirements to find the potentially harmful bugs. we can say that-"How much is too much for the system".

2.4. Difference between function testing and regression testing

Functional Testing: This test is performed to see weather the program is working as per the given flow. functionality is working correctly or not as per requiremnet.
Regression Testing: This test is performed during modification stage. where the applied changes impact the change in working of the whole project or not. Means weather the modification caused errors in existing working of the project or not

2.5. Difference between actual result and expect result

Actual result is the behavior produced/observed when a component or system is tested. It’s like “what it actually look like” status.
Expect result is the behavior predicted by the specification of the component or system under specified conditions. It’s like “what it suppose to be” status

2.6. Did white box testing means testing of code

Yes ,it test the logic of the code

heck

JOBSDB_joyce

2.7. What are the critical things you listed in the performance test result

1.       Concurrent users

2.       Throughout

3.       Server status such as CPU usage,Memory

4.       Response times

5.       Time lapses

6.       Test environment

2.8. What are contents of defects/bugs

A software bug is the common term used to describe an error flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways.
Content of bugs

1.       Bug ID

2.       Bug Title

3.       Summary: expected result, actual result

4.       Priority

5.       Severity

6.       Status:Open/fix/close/holdon/non-reproduce

7.       Software Version

8.       Platform and OS

9.       Component

10.    Assign To

11.    Environment

12.    Reproduce Steps

13.    Supporting files, such as snapshot

2.9. What are contents of test cases

1.       Test Case ID:

2.       Case Name

3.       Priority

4.       Test step

5.       Test Execution

6.       Expected Results

7.       Actual Results

8.       Revision history

9.       Environment

10.    Run time

11.    Name of tester, date

2.10. What is test plan? Have you ever written test plan?

A test plan is a document detailing a systematic approach to testing a system such as a machine or software.
Contents of test plan:

1.       Test scope

2.       Test strategy: integrate testing, system testing, performance testing, security testing

3.       Test Risk

4.       Test resource

5.       Test time line

6.       Sign off critical

2.11. What is the scope of testing

The scope of testing is the boundaries of testing, what will be tested and what will not be tested

2.12. What does your test report look like

1.       the scope of testing

2.       test enviroment

3.       Detailed Test result:the case execution and their status

4.       bug quantity and severity

5.       Suggestion

2.13. What is bug triage and triage group? How to resolve conflict when verifying it is a bug or not

Triage is a process of identify or verify the bugs based on the information of the bug. Whenever we have disagreement to indentify the bug or for a very complex bug, we assign the bug to the triage group, a group of Sr. developers, testers, and leads, to verify it.

2.14. How to know your test cases are too many or too less

Verify the test cases against the scope of the testing and function requirement

2.15. How to ensure the test coverage

1.       Ensure that the documents defining the business and customer requirements are complete and correct.

2.       Ensure that testers themselves have thoroughly read and understood the documents.

3.       Prepare a clear cut scope of testing based on product documents.

4.       The strategy and Test Planning is as per system requirements.

5.       Decide test methodology and test tools (if any), and test schedule.

6.       Prepare Test Cases based on business rules and customer requirements.

7.       Ensure that the test cases are extensive and sensible to cover the complete requirements testing.

8.       Ensure that during testing no changes in the test environment (coding etc.) is done by development team.

9.       Ensure that development team representatives (1 or all) are present during the complete testing.

10.    Create Test Scenarios based on test cases.

11.    Observe the result of each test case and record it accordingly.

12.    Prepare a comprehensive and detailed test report explaining each of the test case, scenario and its result elaborately.

13.    Ensure that all bugs reported should make sense, no duplication/overlapping

14.    The final report submitted should clearly state the areas, reason, impact not covered under testing if avaliable.

15.    Ensure that you have a tentative plan from the dev team when they're fixing all bugs and submitting it back to testing team.

16.    Verify all bugs fixed and ensure that the development team is sitting with testers during verification.

2.16. How to make sure/verify that your testers are blocked by error

1.       Verify the build by running build verification test cases

2.       Verify the test case steps, script, and data. If the data is spoofed, we also need to verify the script for spoofing the data

3.       Rerun the test cases by other tester (other environment if there is as alternative) for double c

candyling5260

Hello, Joyce, 你现在还在深圳的JOBSDB吗？那边有没有Testing team呀？上面的面试题是JOBSDB的面试题吗？

anna9603

very good! very useful!