[Hỗ trợ - Phỏng vấn] Thử sức của bạn qua một số bài test online (Tiếng Anh)

Truy cập địa chỉ sau: http://tools.people-centric.ro/index.php?option=com_otests&view=order&lang=en-GB

[Hỗ trợ - Phỏng vấn] Interview Questions and Answers

 

SQL Expert:

• SQL SERVER – 2008 – Interview Questions and Answers Complete List Download

 

Tester (QA/QC):

• Câu hỏi phỏng vấn 1 (Có kèm câu trả lời)


• Câu hỏi phỏng vấn 2 (Có kèm câu trả lời)


• Câu hỏi phỏng vấn 3 (P1) (Có kèm câu trả lời)


• Câu hỏi phỏng vấn 3 (P2) (Có kèm câu trả lời)


• Câu hỏi phỏng vấn 4 (Có kèm câu trả lời)


• Câu hỏi phỏng vấn 5 (Có kèm câu trả lời)


• Câu hỏi phỏng vấn 6 (Có kèm câu trả lời)


• Câu hỏi phỏng vấn 7 (Có kèm câu trả lời)


• Một số câu hỏi phỏng vấn khác


• Giới thiệu một số test tool công ty đang xài

 

Phỏng vấn tổng quát:

• Phỏng vấn tổng quát cho một lập trình viên

Một số sách chứa các câu hỏi & câu trả lời được sử dụng trong phỏng vấn (Nhấn vào link để tới sách bạn cần tìm)


Sẽ cập nhật đầy đủ các link để down trên megaupload, megafire, rapidshare,... trong một thời gian gần nhất. Hiện giờ một số link đã download được, một số vẫn đang link tới amazon do đó các bạn chưa download được.

	Cracking the Coding Interview, Fourth Edition: 150 Programming Interview Questions and Solutions (MU/FS) Gayle Laakmann
	Programming Interviews Exposed: Secrets to Landing Your Next Job, 2nd Edition (Programmer to Programmer) (MU) Eric Giguere
	Algorithms For Interviews Amit Prakash
	Programming Pearls (2nd Edition) Jon Louis Bentley
	Puzzles for Programmers and Pros (ES/RS) Dennis Elliott Shasha
	Cracking the C, C++, and Java Interview Leonard G. Marks
	How Would You Move Mount Fuji?: Microsoft's Cult of the Puzzle -- How the World's Smartest Companies Select the Most Creative Thinkers (www.ntu.edu.vn) William Poundstone
	C & C++ Interview Questions You'll Most Likely Be Asked Vibrant Publishers
	Ace the IT Interview (Ace the It Job Interview) (MU) Paula Moreira
	Masterminds of Programming: Conversations with the Creators of Major Programming Languages (Theory in Practice (O'Reilly)) (MF) Federico Biancuzzi
	Coders at Work: Reflections on the Craft of Programming (FS) Peter Seibel
	Java / J2EE Interview Questions You'll Most Likely Be Asked Vibrant Publishers
	Hibernate, Spring & Struts Interview Questions You'll Most Likely Be Asked Vibrant Publishers
	Lotus Domino Programming Interview Questions, Answers, and Explanations: Lotus Domino Certification Review Terry Sanchez-Clark
	PHP MySQL Web Programming Interview Questions, Answers, and Explanations: PHP MySQL FAQ Jim Stewart
	Java/J2EE Job Interview Companion Arulkumaran Kumaraswamipillai
	HTML, XHTML & CSS Interview Questions You'll Most Likely Be Asked Vibrant Publishers

 

 

Nếu bạn phát hiện link nào không thể download được, vui lòng báo cho tôi theo địa chỉ email: dotri84@yahoo.com . Tôi sẽ update lại link hoặc gởi ebook trực tiếp cho bạn. Cám ơn. (If you discover any broken links, please notice to me at dotri84@yahoo.com . I will update links or send ebooks directly to you. Thanks.)

[Hỗ trợ - Phỏng vấn] 50 câu hỏi phỏng vấn thường gặp (Tiếng anh)

Review these typical interview questions and think about how you would
answer them. Read the questions listed; you will also find some
strategy suggestions with it.

(Excerpted from the book The Accelerated Job Search by Wayne D. Ford, Ph.D, published by The Management Advantage, Inc.)

1. Tell me about yourself:
The most often asked question in interviews. You need to have a short
statement prepared in your mind. Be careful that it does not sound
rehearsed. Limit it to work-related items unless instructed otherwise.
Talk about things you have done and jobs you have held that relate to
the position you are interviewing for. Start with the item farthest
back and work up to the present.


2. Why did you leave your last job?
Stay positive regardless of the circumstances. Never refer to a major
problem with management and never speak ill of supervisors, co-workers
or the organization. If you do, you will be the one looking bad. Keep
smiling and talk about leaving for a positive reason such as an
opportunity, a chance to do something special or other forward-looking
reasons.

3. What experience do you have in this field?
Speak about specifics that relate to the position you are applying for.
If you do not have specific experience, get as close as you can.

4. Do you consider yourself successful?
You should always answer yes and briefly explain why. A good
explanation is that you have set goals, and you have met some and are
on track to achieve the others.

5. What do co-workers say about you?
Be prepared with a quote or two from co-workers. Either a specific
statement or a paraphrase will work. Jill Clark, a co-worker at Smith
Company, always said I was the hardest workers she had ever known. It
is as powerful as Jill having said it at the interview herself.

6. What do you know about this organization?
This question is one reason to do some research on the organization
before the interview. Find out where they have been and where they are
going. What are the current issues and who are the major players?

7. What have you done to improve your knowledge in the last year?
Try to include improvement activities that relate to the job. A wide
variety of activities can be mentioned as positive self-improvement.
Have some good ones handy to mention.

8. Are you applying for other jobs?
Be honest but do not spend a lot of time in this area. Keep the focus
on this job and what you can do for this organization. Anything else is
a distraction.

9. Why do you want to work for this organization?
This may take some thought and certainly, should be based on the
research you have done on the organization. Sincerity is extremely
important here and will easily be sensed. Relate it to your long-term
career goals.

10. Do you know anyone who works for us?
Be aware of the policy on relatives working for the organization. This
can affect your answer even though they asked about friends not
relatives. Be careful to mention a friend only if they are well thought
of.

11. What kind of salary do you need?
A loaded question. A nasty little game that you will probably lose if
you answer first. So, do not answer it. Instead, say something like,
That’s a tough question. Can you tell me the range for this position?
In most cases, the interviewer, taken off guard, will tell you. If not,
say that it can depend on the details of the job. Then give a wide
range.

12. Are you a team player?
You are, of course, a team player. Be sure to have examples ready.
Specifics that show you often perform for the good of the team rather
than for yourself are good evidence of your team attitude. Do not brag,
just say it in a matter-of-fact tone. This is a key point.

13. How long would you expect to work for us if hired?
Specifics here are not good. Something like this should work: I’d like
it to be a long time. Or As long as we both feel I’m doing a good job.

14. Have you ever had to fire anyone? How did you feel about that?
This is serious. Do not make light of it or in any way seem like you
like to fire people. At the same time, you will do it when it is the
right thing to do. When it comes to the organization versus the
individual who has created a harmful situation, you will protect the
organization. Remember firing is not the same as layoff or reduction in
force.

15. What is your philosophy towards work?
The interviewer is not looking for a long or flowery dissertation here.
Do you have strong feelings that the job gets done? Yes. That’s the
type of answer that works best here. Short and positive, showing a
benefit to the organization.

16. If you had enough money to retire right now, would you?
Answer yes if you would. But since you need to work, this is the type
of work you prefer. Do not say yes if you do not mean it.

17. Have you ever been asked to leave a position?
If you have not, say no. If you have, be honest, brief and avoid saying
negative things about the people or organization involved.

18. Explain how you would be an asset to this organization
You should be anxious for this question. It gives you a chance to
highlight your best points as they relate to the position being
discussed. Give a little advance thought to this relationship.

19. Why should we hire you?
Point out how your assets meet what the organization needs. Do not
mention any other candidates to make a comparison.

20. Tell me about a suggestion you have made
Have a good one ready. Be sure and use a suggestion that was accepted
and was then considered successful. One related to the type of work
applied for is a real plus.

21. What irritates you about co-workers?
This is a trap question. Think real hard but fail to come up with
anything that irritates you. A short statement that you seem to get
along with folks is great.

22. What is your greatest strength?
Numerous answers are good, just stay positive. A few good examples:
Your ability to prioritize, Your problem-solving skills, Your ability
to work under pressure, Your ability to focus on projects, Your
professional expertise, Your leadership skills, Your positive attitude

23. Tell me about your dream job.
Stay away from a specific job. You cannot win. If you say the job you
are contending for is it, you strain credibility. If you say another
job is it, you plant the suspicion that you will be dissatisfied with
this position if hired. The best is to stay genetic and say something
like: A job where I love the work, like the people, can contribute and
can’t wait to get to work.

24. Why do you think you would do well at this job?
Give several reasons and include skills, experience and interest.

25. What are you looking for in a job?
See answer # 23

26. What kind of person would you refuse to work with?
Do not be trivial. It would take disloyalty to the organization,
violence or lawbreaking to get you to object. Minor objections will
label you as a whiner.

27. What is more important to you: the money or the work?
Money is always important, but the work is the most important. There is
no better answer.

28. What would your previous supervisor say your strongest point is?
There are numerous good possibilities:
Loyalty, Energy, Positive attitude, Leadership, Team player, Expertise,
Initiative, Patience, Hard work, Creativity, Problem solver

29. Tell me about a problem you had with a supervisor
Biggest trap of all. This is a test to see if you will speak ill of
your boss. If you fall for it and tell about a problem with a former
boss, you may well below the interview right there. Stay positive and
develop a poor memory about any trouble with a supervisor.

30. What has disappointed you about a job?
Don’t get trivial or negative. Safe areas are few but can include:
Not enough of a challenge. You were laid off in a reduction Company did
not win a contract, which would have given you more responsibility.

31. Tell me about your ability to work under pressure.
You may say that you thrive under certain types of pressure. Give an
example that relates to the type of position applied for.

32. Do your skills match this job or another job more closely?
Probably this one. Do not give fuel to the suspicion that you may want
another job more than this one.

33. What motivates you to do your best on the job?
This is a personal trait that only you can say, but good examples are:
Challenge, Achievement, Recognition

34. Are you willing to work overtime? Nights? Weekends?
This is up to you. Be totally honest.

35. How would you know you were successful on this job?
Several ways are good measures:
You set high standards for yourself and meet them. Your outcomes are a
success.Your boss tell you that you are successful

36. Would you be willing to relocate if required?
You should be clear on this with your family prior to the interview if
you think there is a chance it may come up. Do not say yes just to get
the job if the real answer is no. This can create a lot of problems
later on in your career. Be honest at this point and save yourself
future grief.

37. Are you willing to put the interests of the organization ahead of your own?
This is a straight loyalty and dedication question. Do not worry about
the deep ethical and philosophical implications. Just say yes.

38. Describe your management style.
Try to avoid labels. Some of the more common labels, like progressive,
salesman or consensus, can have several meanings or descriptions
depending on which management expert you listen to. The situational
style is safe, because it says you will manage according to the
situation, instead of one size fits all.

39. What have you learned from mistakes on the job?
Here you have to come up with something or you strain credibility. Make
it small, well intentioned mistake with a positive lesson learned. An
example would be working too far ahead of colleagues on a project and
thus throwing coordination off.

40. Do you have any blind spots?
Trick question. If you know about blind spots, they are no longer blind
spots. Do not reveal any personal areas of concern here. Let them do
their own discovery on your bad points. Do not hand it to them.

41. If you were hiring a person for this job, what would you look for?
Be careful to mention traits that are needed and that you have.

42. Do you think you are overqualified for this position?
Regardless of your qualifications, state that you are very well
qualified for the position.

43. How do you propose to compensate for your lack of experience?
First, if you have experience that the interviewer does not know about,
bring that up: Then, point out (if true) that you are a hard working
quick learner.

44. What qualities do you look for in a boss?
Be generic and positive. Safe qualities are knowledgeable, a sense of
humor, fair, loyal to subordinates and holder of high standards. All
bosses think they have these traits.

45. Tell me about a time when you helped resolve a dispute betweenothers.
Pick a specific incident. Concentrate on your problem solving technique
and not the dispute you settled.

46. What position do you prefer on a team working on a project?
Be honest. If you are comfortable in different roles, point that out.

47. Describe your work ethic.
Emphasize benefits to the organization. Things like, determination to
get the job done and work hard but enjoy your work are good.

48. What has been your biggest professional disappointment?
Be sure that you refer to something that was beyond your control. Show
acceptance and no negative feelings.

49. Tell me about the most fun you have had on the job.
Talk about having fun by accomplishing something for the organization.

50. Do you have any questions for me?
Always have some questions prepared. Questions prepared where you will be an asset to the organization are good. How soon will I be able to be productive? and What type of projects will I be able to assist on? are
examples.

[Hỗ trợ - Phỏng vấn] Một số câu hỏi phỏng vấn khác cho Tester (QA/QC)

Một số câu hỏi phỏng vấn khác dành cho Tester (QA/QC):

[scribd id=6689140 key=key-12vrf6m8ymxd2e75ie2j mode=list]

[Hỗ trợ - Phỏng vấn] Một số test tool công ty đang xài

 

• Microsoft Test Manager 2010


• QF-Test - The GUI Test Tool for Java and Web

(Sẽ có bài giới thiệu về các tool test ở trên)

[Hỗ trợ - Phỏng vấn] Testing Interview Questions and Answers – 7

1. What is the role of QA in development project?


Deploy and enforce standards
Continually improve standards, QA process based on previous experiences
Promote effective means for reporting and communication.



 



2. How do you promote the concept of phase containment and defect prevention?


Phase Containment refers to detecting and correcting defects in the same phase in which they’re created.
The purpose of Defect Prevention is to identify the cause of defects and prevent them from recurring.



 



3. What is Walkthrough?


Walkthrough : A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required.

OR

A process in which a developer leads one or more members of the development team through a segment of an artifact that he or she has written while the other members ask questions and make comments about technique, style, possible error, violation of development standards, and other problems.



 



4. What is inspection?


Inspection: An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a moderator, reader, and a recorder to take notes. The subject of the inspection is typically a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything. Attendees should prepare for this type of meeting by reading thru the document; most problems will be found during this preparation. The result of the inspection meeting should be a written report. Thorough preparation for inspections is difficult, painstaking work, but is one of the most cost effective methods of ensuring quality.

OR

Inspection is a formal evaluation technique in which artifacts are examined in detail by a person or group other than the author to detect errors, violations of development standards, and other problems.



 



5. What is Software Review?


Software Review: An evaluation technique that involves the bringing together a group of technical personnel to analyze a software artifact in order to improve its quality.
Review types:
· Informal: adhoc process, no planning, no structure
· Formal (Formal Technical Review): Follow a structured process Produce written report on artifact status Collect and analyze review metrics



 



6. What if the application has functionality that wasn't in the requirements?


It may take serious effort to determine if an application has significant unexpected or hidden functionality, and it would indicate deeper problems in the software development process. If the functionality isn't necessary to the purpose of the application, it should be removed, as it may have unknown impacts or dependencies that were not taken into account by the designer or the customer. If not removed, design information will be needed to determine added testing needs or regression testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality. If the functionality only effects areas such as minor improvements in the user interface, for example, it may not be a significant risk.



 



Security Testing
What is Security Testing?
What is Secure Socket Layer (SSL)? What is does?
What is Firewall?
What is Proxy Server?
What is Digital Certificate and how it is linked to Certificate Authority (CA)?
What is PKI?
What is the difference between HTTP and HTTPS?

[Hỗ trợ - Phỏng vấn] Testing Interview Questions and Answers – 6

1. What is the difference about web-testing and client server testing?


Web applications are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to the interactions between html pages, TCP/IP communications, Internet connections, firewalls, applications that run in web pages (such as applets, javascript, plug-in applications), and applications that run on the server side (such as cgi scripts, database interfaces, logging applications, dynamic page generators, asp, etc.). Additionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes significant differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that testing for web sites can become a major ongoing effort.



 



2. Is a "Fast database retrieval rate" a testable requirement?


This is not a testable requirement. ‘Fast’ is a subjective term. It could mean different things depending on a person’s perception. For a requirement to be testable, it should be quantified and repeatable, so that the actual value could be measured against the expected value.



 



3. What different type of test cases you wrote in the test plan?


Test cases for interface, functionality, security, load and performance testing.



 



4. What development model should programmers and the test group use?


A Development Model, which helps adopt a structured approach in assessment, design, integration and implementation of a project and in extending relevant training and support. Each of these stages is necessarily accompanied with client inputs, checkpoints and reviews to ensure successful systems implementation.

Basically there are many types of development models to support the development of high-quality software products. The two most widely used models are Waterfall and Spiral development model.
Waterfall development model encourages the development team to specify the business functionality of the software prior to developing a system.
Spiral development model combines the waterfall development model and the prototype approach, which is a series of partial implementations of the product.

A typical project may include some or all of the following phases:
· requirements analysis
· functional specifications
· architectural design
· detailed design
· coding
· unit testing
· integration testing
· deployment and
· maintenance.



 



5. What are the key challenges of load testing?


The key challenges to load testing is handling various components from various vendors.



 



6. Have you done explanatory or specification-driven testing?


Yes, specification-driven testing means checking the product’s confirmance with every statement in every spec, requirements docuement, etc.



 

[Hỗ trợ - Phỏng vấn] Testing Interview Questions and Answers – 5

1. How do you analyze your test results? what metrics do you try to provide?
   OR
   How do you view test results?


Test log is created for analyzing the test results.This is a chronological record of the Test executions and events that happened during testing. It includes the following sections:

Description: What’s being tested, including Version ID, where testing is being done, what hardware and all other configuration information.
Activity and Event Entries: What happened including Execution Description: The procedure used.
Procedure Result: What happened. What did you see and where did you store the output?
Environment Information: Any changes (hardware substitution) made specifically for this test.
Unexpected Events: What happened before and after problem/bug occurred.
Incident/Bug Report Identifiers: Problem Report number



 



2. If you come onboard, give me a general idea of what your first overall tasks will be as far as as starting a quality effort?


Try to learn about the application, Environment and Prototypes to have the better understanding of application and existing testing efforts



 



3. How do you differentiate the roles of Quality Assurance Manager and Project Manager?


Quality assurance manager responsibilites includes seting up the standards, the methodology and the strategies for testing the application and providing guidelines to the QA team. Project Manager is reponsible to testing and development activities.



 



4. What do you like about QA?


QA is the field where in one will be working to multiple environments and can learn more.



 



5. Who in the company is responsible for Quality?


Both development and quality assurance departments are responsible for the final product quality.



 



6. Should we test every possible combination/scenario for a program?


Ideally, yes we should test every possible scenario, but this may not always be possible. It depends on many factors viz., deadlines, budget, complexity of software and so on. In such cases, we have to prioritize and thoroughly test the critical areas of the application.



 



7. What is client-server architecture?


Client-server architecture, a client is defined as a requester of services and a server is defined as the provider of services. Communication takes place in the form a request message from the client to the server asking for some work to be done. Then the server does the work and sends back the reply.



 



8. How Intranet is different from client-server?


Internet applications are essentially client/server applications - with web servers and 'browser'



 



9. What is three-tier and multi-tier architecture?


A design which separate (1) client, (2) application, and (3) data each into their own separate areas which allows for more scalable, robust solutions

A three-tier system is one that has presentation components, business logic and data access physically running on different platforms. Web applications are perfect for three-tier architecture, as the presentation layer is necessarily separate, and the business and data components can be divided up much like a client-server application



 

[Hỗ trợ - Phỏng vấn] Testing Interview Questions and Answers – 4

1. What is user acceptance testing?


It is also called as Beta Testing. Once System Testing is done and the system seems stable to the developers and testers, system engineers usually invite the end users of the software to see if they like the software. If the users like the software the way it is then software will be delivered to the user. Otherwise necessary changes will be made to the software and software will pass through all phases of testing again.



 



2. What is manual testing and what is automated testing?


Manual testing involves testing of software application by manually performing the actions on the AUT based on test plans.
Automated testing involves testing of a software application by performing the actions on the AUT by using automated testing tool (such as WinRunner, LoadRunner) based on test plans



 



3. What are the entrance and exit criteria in the system test?


Entrance and exit criteria of each testing phase is written in the master test plan.

Enterence Criteria:
- Integration exit criteria have been successfully met.
- All installation documents are completed.
- All shippable software has been successfully built
- Syate, test plan is baselined by completing the walkthrough of the test plan.
- Test environment should be setup.
- All severity 1 MR’s of integration test phase should be closed.
Exit Criteria:
- All the test cases in the test plan should be executed.
- All MR’s/defects are either closed or deferred.
- Regression testing cycle should be executed after closing the MR’s.
- All documents are reviewed, finilized and signed-off.



 



4. If there are no requirements, how will you write your test plan?


If there are no requirements we try to gather as much details as possible from:
· Business Analysts
· Developers (If accessible)
· Previous Version documentation (if any)
· Stake holders (If accessible)
· Prototypes.



 



5. What is smoke testing?


The smoke test should exercise the entire system from end to end. It does not have to be exhaustive, but it should be capable of exposing major problems. The smoke test should be thorough enough that if the build passes, you can assume that it is stable enough to be tested more thoroughly.

The daily build has little value without the smoke test. The smoke test is the sentry that guards against deteriorating product quality and creeping integration problems. Without it, the daily build becomes just a time-wasting exercise in ensuring that you have a clean compile every day.

The smoke test must evolve as the system evolves. At first, the smoke test will probably test something simple, such as whether the system can say, "Hello, World." As the system develops, the smoke test will become more thorough. The first test might take a matter of seconds to run; as the system grows, the smoke test can grow to 30 minutes, an hour, or more.



 



6. What is soak testing?


The software system will be run for a total of 14 hours continuously. If the system is a control system, it will be used to continuously move each of the instrument mechanisms during this time. Any other system will be expected to perform its intended function continuously during this period. The software system must not fail during this period.



 



7. What is a pre-condition data?


Data required to setup in the system before the test execution.



 



8. What are the different documents in QA?


Requirements Document, Test Plan, Test cases, Test Metrics, Task Distribution Diagrams ( Performance), Transaction Mix, User Profiles, Test Log, Test Incident Report, Test Summary Report



 



9. How do you rate yourself in software testing


excellent



 



10. What are the best web sites that you frequently visit to upgrade your QA skills?


http://www.softwareqatest.com/
http://sqp.asq.org/



 



11. Is defect resolution a technical skill or interpersonal skill from QA view point?


It is a combination of both , because it deals with the interaction with developer either directly or indirectly which needs interpersonal skills and is also based on the skills of the QA personnel to provide a detailed proof to the developer like snap shots and system resource utilization and some suggestions which are little bit technical.



 



12. What is End to End business logic testing?


Testing the integration of all the modules of the AUT.



 



13. What is an equivalence class?


A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification



 

[Hỗ trợ - Phỏng vấn] Testing Interview Questions and Answers – 3 (Part 2)

1. What is test Metrics?


Test metrics contains follwoing details:
Total test
Test run
Test passed
Test failed
Tests deferred
Test passed the first time



 



2. What is the use of Metrics?


Provide the accurate measurement of test coverage.



 



3. If you have shortage of time, how would you prioritize you testing?


Use risk analysis to determine where testing should be focused. Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. Considerations can include:
Which functionality is most important to the project's intended purpose?
Which functionality is most visible to the user?
Which functionality has the largest safety impact?
Which functionality has the largest financial impact on users?
Which aspects of the application are most important to the customer?
Which aspects of the application can be tested early in the development cycle?
Which parts of the code are most complex, and thus most subject to errors?
Which parts of the application were developed in rush or panic mode?
Which aspects of similar/related previous projects caused problems?
Which aspects of similar/related previous projects had large maintenance expenses?
Which parts of the requirements and design are unclear or poorly thought out?
What do the developers think are the highest-risk aspects of the application?
What kinds of problems would cause the worst publicity?
What kinds of problems would cause the most customer service complaints?
What kinds of tests could easily cover multiple functionalities?
Which tests will have the best high-risk-coverage to time-required ratio?



 



4. What is the impact of environment on the actual results of performance testing?


Environment plays an important role in the results and effectiveness of test, particularly in the area of performance testing. Some of the factors will be under our control, while others will not be. These may involve the DBMS, the operating system or the network. Some of the items that we cannot control unless you can secure a stand-alone environment (which will generally be unrealistic) are:
- Other traffic on the network
- Other process running on the server
- Other process running on the DBMS



 



5. What is stress testing, performance testing, Security testing, Recovery testing and volume testing?


Stress testing: Testing the system if it can handle peak usage period loads that result from large number of simultaneous users, transactions or devices. Monitoring should be performed for throughput and system stability.

Performance Testing: Testing the system whether the system functions are being performed in an acceptable timeframe under simultaneous user load. Timings for both read and update transactions should be gathered to determine whether. This should be done stand-alone and then in a multi-user environment to determine the transaction throughput.

Security Testing: Testing the system for its security from unauthorized use and unauthorized data access.

Recovery Testing: Testing a system to see how it responds to errors and abnormal conditions, such as system crash, loss of device, communications, or power.

Volume Testing: Testing to the system to determine if it can correctly process large volumes of data fed to the system. Systems can often respond unpredictably when large volume causes files to overflow and need extensions.



 



6. What criteria you will follow to assign severity and due date to the MR?


Defects (MR) are assigned severity as follows:
Critical: show stoppers (the system is unusable)
High: The system is very hard to use and some cases are prone to convert to critical issues if not taken care of.
Medium: The system functionality has a major bug but is not too critical but needs to be fixed in order for the AUT to go to production environment.
Low: cosmetic (GUI related)



 

[Hỗ trợ - Phỏng vấn] Testing Interview Questions and Answers – 3 (Part 1)

1. Where do you get your expected results?


User requirement document



 



2. If automating-what is your process for determining what to automate and in what order? OR
   Can you automate all the test scripts? Explain ? OR
   How do you plan test automation? OR
   What criteria do you use when determining when to automate a test or leave it manual?


Test that need to be run for every build of the application
Tests that use multiple data values for the same actions( data driven tests)
Tests that require detailed information from application internals
Stress/ load testing



 



3. If you’re given a program that will average student grades, what kinds of inputs would you use?/li>
   
   Name of student, Subject, Score
   
   

    

   
   
4. What is the exact difference between Integration and System testing, give me examples with your project?


Integration testing: An orderly progression of testing in which software components or hardware components, or both are combined and tested until the entire system has been integrated.
System testing: The Process of testing an integrated hardware and software system to verify that the system meets its specified requirements.



 



5. How do you go about testing a project?


Analyze user requirement documents and other documents like software specifications, design document etc.
Write master test plan which describe the scope, objective, strategy, risk/contingencies, resources
Write system test plan and detailed test cases
Execute test cases manually and compare actual results against expected results.
Identify mismatches, report defect to the development team using defect reporting tool.
Track defect, perform regression test to verify that defect is fixed and did not disturb other parts of the application.
Once all the defects are closed and application is stabilized, automate the test scripts for regression and performance testing.



 



6. What are negative scenarios?


Testing to see whether the application is not doing what it is not suppose to do.



 



7. How do you go about testing a web application?


We check for User interface, Functionality, Interface testing, Compatibility, Load/Stress, and Security.



 



8. Difference between Black and White box testing?


Black box testing: Functional testing based on requirements with no knowledge of the internal program structure or data. Also known as closed-box testing.
White Box testing: Testing approaches that examine the program structure and device test data from the program logic.



 



9. What is configuration management? Tools used?


Configuration management: helps teams control their day-to-day management of software development activities as software is created, modified, built and delivered. Comprehensive software configuration management includes version control, workspace management, build management, and process control to provide better project control and predictability



 



10. What are Individual test case and Workflow test case? Why we do workflow scenarios


An individual test is one that is for a single features or requirement. However, it is important that related sequences of features be tested as well, as these correspond to units of work that user will typically perform. It will be important for the system tester to become familiar with what users intend to do with the product and how they intend to do it. Such testing can reveal errors that might not ordinarily be caught otherwise. For example while each operations in a series might produce the correct results it is possible that intermediate results get lost or corrupted between operations.



 



11. What are the testing tools are you familiar with?


TestDirector, WinRunner, LoadRunner, Rational RequisitPro, Rational TestManager, Rational Robot, Rational ClearQuest and SilkTest.



 



12. How did you use automating testing tools in your job?


Automating testing tools are used for preparing and managing regression test scripts and load and perofromenance tests.



 



13. What is data-driven automation?


If you want to perform the same operations with differnet set of data, we can create data driven test with loop. In each iteration test is driven by differnet set of data. In order for automation to use data to drive the test, we must subsitute the fixed values in the test with variables.



 



14. Describe me the difference between validation and verification?


Verification: typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings.

Validation: typically involves actual testing and takes place after verifications are completed. The term 'IV & V' refers to Independent Verification and Validation



 



15. Is coding required in SQA robot?


Yes, to enhance the script for testing the business logic, and when we write the user define the functions.



 



16. What do you mean by "set up the test environment and provide full platform support"?


We need to provide the following for setting up the environment
1) Required software
2) Required hardware
3) Required testing tools
4) Required test data
After providing these we need to provide support for any problems that occur during the testing process.



 



17. What are the two ways to copy a file in windows?


1) Using the copy menu item in the edit menu.
2) By dragging the file where ever you want to copy it like a floppy



 



18. If the functionality of an application had an inbuilt bug because of which the test script fails, would you automate the test?


No, we do the automation once the application is tested manually and it is stabilized. Automation is for regression testing.



 



19. What is the bug reporting tool used?


Rational ClearQuest
TestDirectror
PVCS Tracker



 



20. Did use SQA Manager?


Yes. For creating test plan and defect reporting/tracking.



 



21. You find a bug and the developer says "It’s not possible" what do u do?


I’ll discuss with him under what conditions (working environment) the bug was produced. I’ll provide him with more details and the snapshot of the bug.



 



22. How do you help developer to track the fault s in the software?


By providing him with details of the defects which include the environment, test data, steps followed etc… and helping him to reproduce the defect in his environment.



 



23. Were you able to meet deadlines?


Absolutely.



 



24. What is Polymorphism? Give example.


In object-oriented programming, polymorphism refers to a programming language's ability to process objects differently depending on their data type or class. More specifically, it is the ability to redefine methods for derived classes.
For example, given a base class shape, polymorphism enables the programmer to define different circumference methods for any number of derived classes, such as circles, rectangles and triangles.
No matter what shape an object is, applying the circumference method to it will return the correct results. Polymorphism is considered to be a requirement of any true object-oriented programming language (OOPL).



 



25. What are the different types of MRs?


MR for suggestions,
MR for defect reports,
MR for documentations changes



 

[Hỗ trợ - Phỏng vấn] Testing Interview Questions and Answers – 3

1. Where do you get your expected results?


User requirement document



 



2. If automating-what is your process for determining what to automate and in what order? OR
   Can you automate all the test scripts? Explain ? OR
   How do you plan test automation? OR
   What criteria do you use when determining when to automate a test or leave it manual?


Test that need to be run for every build of the application
Tests that use multiple data values for the same actions( data driven tests)
Tests that require detailed information from application internals
Stress/ load testing



 



3. If you’re given a program that will average student grades, what kinds of inputs would you use?/li>
   
   Name of student, Subject, Score
   
   

    

   
   
4. What is the exact difference between Integration and System testing, give me examples with your project?


Integration testing: An orderly progression of testing in which software components or hardware components, or both are combined and tested until the entire system has been integrated.
System testing: The Process of testing an integrated hardware and software system to verify that the system meets its specified requirements.



 



5. How do you go about testing a project?


Analyze user requirement documents and other documents like software specifications, design document etc.
Write master test plan which describe the scope, objective, strategy, risk/contingencies, resources
Write system test plan and detailed test cases
Execute test cases manually and compare actual results against expected results.
Identify mismatches, report defect to the development team using defect reporting tool.
Track defect, perform regression test to verify that defect is fixed and did not disturb other parts of the application.
Once all the defects are closed and application is stabilized, automate the test scripts for regression and performance testing.



 



6. What are negative scenarios?


Testing to see whether the application is not doing what it is not suppose to do.



 



7. How do you go about testing a web application?


We check for User interface, Functionality, Interface testing, Compatibility, Load/Stress, and Security.



 



8. Difference between Black and White box testing?


Black box testing: Functional testing based on requirements with no knowledge of the internal program structure or data. Also known as closed-box testing.
White Box testing: Testing approaches that examine the program structure and device test data from the program logic.



 



9. What is configuration management? Tools used?


Configuration management: helps teams control their day-to-day management of software development activities as software is created, modified, built and delivered. Comprehensive software configuration management includes version control, workspace management, build management, and process control to provide better project control and predictability



 



10. What are Individual test case and Workflow test case? Why we do workflow scenarios


An individual test is one that is for a single features or requirement. However, it is important that related sequences of features be tested as well, as these correspond to units of work that user will typically perform. It will be important for the system tester to become familiar with what users intend to do with the product and how they intend to do it. Such testing can reveal errors that might not ordinarily be caught otherwise. For example while each operations in a series might produce the correct results it is possible that intermediate results get lost or corrupted between operations.



 



11. What are the testing tools are you familiar with?


TestDirector, WinRunner, LoadRunner, Rational RequisitPro, Rational TestManager, Rational Robot, Rational ClearQuest and SilkTest.



 



12. How did you use automating testing tools in your job?


Automating testing tools are used for preparing and managing regression test scripts and load and perofromenance tests.



 



13. What is data-driven automation?


If you want to perform the same operations with differnet set of data, we can create data driven test with loop. In each iteration test is driven by differnet set of data. In order for automation to use data to drive the test, we must subsitute the fixed values in the test with variables.



 



14. Describe me the difference between validation and verification?


Verification: typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings.

Validation: typically involves actual testing and takes place after verifications are completed. The term 'IV & V' refers to Independent Verification and Validation



 



15. Is coding required in SQA robot?


Yes, to enhance the script for testing the business logic, and when we write the user define the functions.



 



16. What do you mean by "set up the test environment and provide full platform support"?


We need to provide the following for setting up the environment
1) Required software
2) Required hardware
3) Required testing tools
4) Required test data
After providing these we need to provide support for any problems that occur during the testing process.



 



17. What are the two ways to copy a file in windows?


1) Using the copy menu item in the edit menu.
2) By dragging the file where ever you want to copy it like a floppy



 



18. If the functionality of an application had an inbuilt bug because of which the test script fails, would you automate the test?


No, we do the automation once the application is tested manually and it is stabilized. Automation is for regression testing.



 



19. What is the bug reporting tool used?


Rational ClearQuest
TestDirectror
PVCS Tracker



 



20. Did use SQA Manager?


Yes. For creating test plan and defect reporting/tracking.



 



21. You find a bug and the developer says "It’s not possible" what do u do?


I’ll discuss with him under what conditions (working environment) the bug was produced. I’ll provide him with more details and the snapshot of the bug.



 



22. How do you help developer to track the fault s in the software?


By providing him with details of the defects which include the environment, test data, steps followed etc… and helping him to reproduce the defect in his environment.



 



23. Were you able to meet deadlines?


Absolutely.



 



24. What is Polymorphism? Give example.


In object-oriented programming, polymorphism refers to a programming language's ability to process objects differently depending on their data type or class. More specifically, it is the ability to redefine methods for derived classes.
For example, given a base class shape, polymorphism enables the programmer to define different circumference methods for any number of derived classes, such as circles, rectangles and triangles.
No matter what shape an object is, applying the circumference method to it will return the correct results. Polymorphism is considered to be a requirement of any true object-oriented programming language (OOPL).



 



25. What are the different types of MRs?


MR for suggestions,
MR for defect reports,
MR for documentations changes



 

[Hỗ trợ - Phỏng vấn] Interview Questions and Answers

 

SQL Expert:

• SQL SERVER – 2008 – Interview Questions and Answers Complete List Download

 

Tester (QA/QC):

• Câu hỏi phỏng vấn 1 (Có kèm câu trả lời)


• Câu hỏi phỏng vấn 2 (Có kèm câu trả lời)


• Câu hỏi phỏng vấn 3 (Có kèm câu trả lời)

 

Phỏng vấn tổng quát:

• Phỏng vấn tổng quát cho một lập trình viên

[Hỗ trợ - Phỏng vấn] Testing Interview Questions and Answers – 2

1. What are CMM and CMMI? What is the difference?


The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

The Capability Maturity Model Integration (CMMI) provides the guidance for improving your organization's processes and your ability to manage the development, acquisition, and maintenance of products and services. CMM Integration places proven practices into a structure that helps your organization assess its organizational maturity and process area capability, establish priorities for improvement, and guide the implementation of these improvements.

The new integrated model (CMMI) uses Process Areas (known as PAs) which are different to the previous model, and covers as well systems as software processes, rather than only software processes as in the SW-CMM.



 



2. Do you have a favorite QA book? Why?


Effective Methods for Software Testing - Perry, William E.

It covers the whole software lifecycle, starting with testing the project plan and estimates and ending with testing the effectiveness of the testing process. The book is packed with checklists, worksheets and N-step procedures for each stage of testing.



 



3. When should testing be stopped?


This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:
- Deadlines (release deadlines, testing deadlines, etc.)
- Test cases completed with certain percentage passed
- Test budget depleted
- Coverage of code/functionality/requirements reaches a specified point
- Bug rate falls below a certain level
- Beta or alpha testing period ends



 



4. When do you start developing your automation tests?


First, the application has to be manually tested. Once the manual testing is over and baseline is established.



 



5. What are positive scenarios?


Testing to see whether the application is doing what it is supposed to do.



 



6. What are negative scenarios?


Testing to see whether the application is not doing what it is not suppose to do.



 



7. What is quality assurance?


The set of support activities (including facilitation, training, measurement and analysis) needed to provide adequate confidence that processes are established and continuously improved in order to produce products that meet specifications and fit for use.



 



8. What is the purpose of the testing?


Testing provides information whether or not a certain product meets the requirements.



 



9. What is the difference between QA and testing?


Quality Assurance is that set of activities that are carried out to set standards and to monitor and improve performance so that the care provided is as effective and as safe as possible. Testing provides information whether or not a certain product meets the requirements. It also provides information where the product fails to meet the requirements.

What are benefits of the test automation?
Fast
Reliable
Repeatable
Programmable
Comprehensive
Reusable



 



10. Describe some problems that you had with automation testing tools


One of the problems with Automation tools is Object recognition



 



11. Can test automation improver test effectiveness?


Yes, because of the advantages offered by test automation, which includes repeatability, consistency, portability and extensive reporting features.



 



12. What are the main use of test automation?


Regression Testing.



 



13. Does automation replace manual testing?


No, it does not. There could be several scenarios that cannot be automated or simply too complicated that manual testing would be easier and cost effective. Further automation tools have several constrains with regard the environment in which they run and IDEs they support.



 



14. How will you choose a tool for test automation?
    OR
    How we decide which automation tool we are going to use for the regression testing?


· Based on risk analysis like: personnel skills, companies software resources
· Based on Cost analysis
· Comparing the tools features with test requirement.
· Support for the applications IDE, support for the application environment/platform.



 



15. What could wrong with automation testing?


There are several things. For ex. Script errors can cause a genuine bug to go undetected or report a bug in the application when the bug does not actually exist.



 



16. How will you describe testing activities?


Testing planning, scripting, execution, defect reporting and tracking, regression testing.



 



17. What type of scripting techniques for test automation do you know?


Modular tests and data driven test



 



18. What are good principles for test scripts?


Portable
Repeatable
Reusable
Maintainable



 



19. What type of document do you need for QA, QC and testing?


Following is the list of documents required by QA and QC teams
Business requirements
SRS
Use cases
Test plan
Test cases



 



20. What are the properties of a good requirement?


Understandable, Clear, Concise, Total Coverage of the application



 



21. What kinds of testing have you done?


Manual, automation, regression, integration, system, stress, performance, volume, load, white box, user acceptance, recovery.



 



22. Have you ever written test cases or did you just execute those written by others?


Yes, I was involved in preparing and executing test cases in all the project.



 



23. How do you determine what to test?


Depending upon the User Requirement document.



 



24. How do you decide when you have ‘tested enough?’


Using Exit Criteria document we can decide that we have done enough testing.



 


Realising you won’t be able to test everything-how do you decide what to test first? OR
What if there isn't enough time for thorough testing? Use risk analysis to determine where testing should be focused. Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgment skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include:
· Which functionality is most important to the project's intended purpose?
· Which functionality is most visible to the user?
· Which functionality has the largest safety impact?
· Which functionality has the largest financial impact on users?
· Which aspects of the application are most important to the customer?
· Which aspects of the application can be tested early in the development cycle?
· Which parts of the code are most complex, and thus most subject to errors?
· Which parts of the application were developed in rush or panic mode?
· Which aspects of similar/related previous projects caused problems?
· Which aspects of similar/related previous projects had large maintenance expenses?
· Which parts of the requirements and design are unclear or poorly thought out?
· What do the developers think are the highest-risk aspects of the application?
· What kinds of problems would cause the worst publicity?
· What kinds of problems would cause the most customer service complaints?
· What kinds of tests could easily cover multiple functionalities?
· Which tests will have the best high-risk-coverage to time-required ratio?


 

[Hỗ trợ - Phỏng vấn] Testing Interview Questions and Answers – 2

1. What are CMM and CMMI? What is the difference?


The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

The Capability Maturity Model Integration (CMMI) provides the guidance for improving your organization's processes and your ability to manage the development, acquisition, and maintenance of products and services. CMM Integration places proven practices into a structure that helps your organization assess its organizational maturity and process area capability, establish priorities for improvement, and guide the implementation of these improvements.

The new integrated model (CMMI) uses Process Areas (known as PAs) which are different to the previous model, and covers as well systems as software processes, rather than only software processes as in the SW-CMM.



 



2. Do you have a favorite QA book? Why?


Effective Methods for Software Testing - Perry, William E.

It covers the whole software lifecycle, starting with testing the project plan and estimates and ending with testing the effectiveness of the testing process. The book is packed with checklists, worksheets and N-step procedures for each stage of testing.



 



3. When should testing be stopped?


This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:
- Deadlines (release deadlines, testing deadlines, etc.)
- Test cases completed with certain percentage passed
- Test budget depleted
- Coverage of code/functionality/requirements reaches a specified point
- Bug rate falls below a certain level
- Beta or alpha testing period ends



 



4. When do you start developing your automation tests?


First, the application has to be manually tested. Once the manual testing is over and baseline is established.



 



5. What are positive scenarios?


Testing to see whether the application is doing what it is supposed to do.



 



6. What are negative scenarios?


Testing to see whether the application is not doing what it is not suppose to do.



 



7. What is quality assurance?


The set of support activities (including facilitation, training, measurement and analysis) needed to provide adequate confidence that processes are established and continuously improved in order to produce products that meet specifications and fit for use.



 



8. What is the purpose of the testing?


Testing provides information whether or not a certain product meets the requirements.



 



9. What is the difference between QA and testing?


Quality Assurance is that set of activities that are carried out to set standards and to monitor and improve performance so that the care provided is as effective and as safe as possible. Testing provides information whether or not a certain product meets the requirements. It also provides information where the product fails to meet the requirements.

What are benefits of the test automation?
Fast
Reliable
Repeatable
Programmable
Comprehensive
Reusable



 



10. Describe some problems that you had with automation testing tools


One of the problems with Automation tools is Object recognition



 



11. Can test automation improver test effectiveness?


Yes, because of the advantages offered by test automation, which includes repeatability, consistency, portability and extensive reporting features.



 



12. What are the main use of test automation?


Regression Testing.



 



13. Does automation replace manual testing?


No, it does not. There could be several scenarios that cannot be automated or simply too complicated that manual testing would be easier and cost effective. Further automation tools have several constrains with regard the environment in which they run and IDEs they support.



 



14. How will you choose a tool for test automation?
    OR
    How we decide which automation tool we are going to use for the regression testing?


· Based on risk analysis like: personnel skills, companies software resources
· Based on Cost analysis
· Comparing the tools features with test requirement.
· Support for the applications IDE, support for the application environment/platform.



 



15. What could wrong with automation testing?


There are several things. For ex. Script errors can cause a genuine bug to go undetected or report a bug in the application when the bug does not actually exist.



 



16. How will you describe testing activities?


Testing planning, scripting, execution, defect reporting and tracking, regression testing.



 



17. What type of scripting techniques for test automation do you know?


Modular tests and data driven test



 



18. What are good principles for test scripts?


Portable
Repeatable
Reusable
Maintainable



 



19. What type of document do you need for QA, QC and testing?


Following is the list of documents required by QA and QC teams
Business requirements
SRS
Use cases
Test plan
Test cases



 



20. What are the properties of a good requirement?


Understandable, Clear, Concise, Total Coverage of the application



 



21. What kinds of testing have you done?


Manual, automation, regression, integration, system, stress, performance, volume, load, white box, user acceptance, recovery.



 



22. Have you ever written test cases or did you just execute those written by others?


Yes, I was involved in preparing and executing test cases in all the project.



 



23. How do you determine what to test?


Depending upon the User Requirement document.



 



24. How do you decide when you have ‘tested enough?’


Using Exit Criteria document we can decide that we have done enough testing.



 


Realising you won’t be able to test everything-how do you decide what to test first? OR
What if there isn't enough time for thorough testing? Use risk analysis to determine where testing should be focused. Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgment skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include:
· Which functionality is most important to the project's intended purpose?
· Which functionality is most visible to the user?
· Which functionality has the largest safety impact?
· Which functionality has the largest financial impact on users?
· Which aspects of the application are most important to the customer?
· Which aspects of the application can be tested early in the development cycle?
· Which parts of the code are most complex, and thus most subject to errors?
· Which parts of the application were developed in rush or panic mode?
· Which aspects of similar/related previous projects caused problems?
· Which aspects of similar/related previous projects had large maintenance expenses?
· Which parts of the requirements and design are unclear or poorly thought out?
· What do the developers think are the highest-risk aspects of the application?
· What kinds of problems would cause the worst publicity?
· What kinds of problems would cause the most customer service complaints?
· What kinds of tests could easily cover multiple functionalities?
· Which tests will have the best high-risk-coverage to time-required ratio?