1. What is Software Testing?

Software Testing is the process of executing a program with the intent of finding
errors. S/T is the process of creating, implementing and evaluating tests.

2. Why Software testing?

S/T is important as it may cause mission failure , impact on operational performance

and reliability if not done properly.

3. what is primary role of software testing?

Determine whether the system meets specifications (procedure view)

Determine whether the system meets business and user meets (customer view)

4. What is Quality?

Customer requirements for first time and every time. Give the customer expectation
products.

5. Why quality?

Quality is the important factor affecting an organization long term performance.

Quality improves productivity and competitiveness in any organization.

6. what is the difference between quality assurance and testing?

QA involves the entire software development process and testing involves operation
of a system or application to evaluate the results certain under conditions.

QA is a process oriented.
Defects prevention based

QC or Testing is a product oriented

Defects detection based

7. What is meant by V-Model Testing and advantages and disadvantages in V-

Model?

Involving software testing in all phases of the software development life cycle. That
means Verification and validation (Verification= development ; Validation= Testing).
 It tells that the testing begins simultaneously with the development. In this model
development stages are linked with testing stages. Virtually it forms a v-shape.

Requirement Study Production Verification Testing

High level design User Acceptance Testing

Low level design System Testing

Unit testing Integration testing

8. What is the differences between static and dynamic testing?

Actually there are two types of testing.

Static testing: Is the process of verifying physical components of system is called

static testing. Static testing refers to testing something that’s non-executing that means
examining and reviewing it.

EX: physical documents: Test Plans, Test Cases or Project oriented documents. In
testing term it is called verification.

Dynamic Testing: Is the process of verifying logical components of system is called

dynamic testing. When we test the software by executing and comparing actual and
expected result is called dynamic testing.

In testing term it is called validation.

Test case Execution, Defect Tracking are the part of Dynamic Testing.
But the Aim of both static and dynamic testing is to find defect. But static testing can
prevent defect at the earlier stage.

9. How can you differentiate black box testing and white box testing? Is white box
and glass box testing same?

In the dynamic testing there are two types of Testing design methods. Functional
testing and structural testing.
Functional testing: functional testing is nothing but testing the application based on
analysis of requirements. Without having internal structural knowledge. Also known
as “Black Box Testing”. In this black box testing it does not need knowledge of
coding. It also called behaviour testing. Also known as close Box testing.
in this method structure of the program is not considered.
 Test cases are decided to based on the requirements or specification of the program or
module.
Structural testing: Testing the application based on analysis of internal structure of
the program. Also known as “White Box Testing” or “Glass Box Testing”.
In this method structure of the program is considered.
Focused on the internal structure of the program.

10. what is the difference between UAT and system testing?

There are 4 levels of testing.

Unit testing
Integration testing
System testing.
User acceptance testing

Unit testing: Test each module individually. Testing done to a unit or smallest piece
of software. Follows a white box testing.

Integration testing: integrate two or more modules. Communicate between the

modules.

Follows a white box testing.

System Testing: Finding the defects. When the system is tested as a whole, this also
called as end to end testing. In this testing tester need to test the application from log-
in to log out.

UAT: User acceptance testing is to get the acceptance from the client. UAT generally
done at client’s environment. Before UAT pre UAT should be done.

11. What are the black box testing techniques ?

Equivalence partition
Boundary analysis
Error guessing
Equivalence portioning: A subset of data that is representative of a larger class.
For example: a program which edits credit limits within a given range ($10,000-
$15,000 would have a 3 equivalence classes)
Less than $10,000 ( Invalid)
Between $10,000-$15,000 (Valid)
More than $15,000 (Invalid).
Boundary analysis: A technique that consist of developing test cases and data that
focus on the input and output boundaries of a given function.
 For example: boundary analysis would test:
Low boundary plus or minus one ($9,999 and $10,001 )
On the boundary ( $10,00 and $15,000)
Upper boundary plus or minus one ( $14,999 and $ 15,001).

12. when system testing required?

Unit test must be completed

Integration test must be completed
Complete software system should be developed
Then after we need a system testing. system testing is nothing but functional testing.

System testing: we have a several stages in system testing

Test plan preparation

Test case design
Test case execution
Test log preparation
Defect tracking
Test report preparation
It’s called Test Plan Life Cycle or Test Process.

13. Briefly explain STLC?

We organised 6 steps.
Test Plan Preparation: Test Plan is nothing but road map of testing activities of the
project. It consist of so many sections.
Purpose
Scope
Test approach
Test strategy
Entry criteria
Resources
Risk analysis
Roles and responsibilities
Exit criteria

Test Case Design: Set of procedures which we execute in our system to find defects
 Test Execution: Execute the test cases.
Test Log Preparation: All pass or fail information will be store in this test log.
Defect Tracking: All the fail test case execution will come under the defect tracking.
Test Report:
This Software Testing Life Cycle is also called Test Process.

14. How do you design a test cases?

Based on the requirements we will write the test cases.

In this process we will consider the positive and negative test cases.

15. what is severity and priority? Its difference

Severity: How much serious the bugs is affecting the functionality of the application.
Severity is given by the tester. Critical, Major, Minor
Priority: How much bugs is affecting the testing, based on severity. Priority will be
given by the developers. High, Medium, Low.

16. What is the regression testing?

Regression testing is nothing but make sure the old functions are working well when
there is a new functions are added or new bug fixed or when there is a code change.
My regression testing is suited for high priority business area. Regression testing
means testing the modified build.

17. What is mean by validation and verification?

Validation: Validation is nothing but checking the user requirements.

Verification: Verification is nothing but checking the user specification.

18. What are the Challenges you think you may face in client location?

Environment Setup

Miscommunication

Mismatched priorities

Performance Lack
 19. What is mean by Matrices ?

Matrices is nothing but a Measurement.

Matrices is a mathematical number that shows a relationship between the two
variables.
It is a informal process.

Matrix is important entity in software testing. Matrices is conduct the all level documents.
Such as test case matrix document and defect matrix document. As a tester I collect the test
case, defect and functional matrices.

20. what is traceability matrix?

A document showing the relationship between test requirements and test cases.

21.  How will you write test cases for a code currently under development?

It’s all depends on the Software Requirements Specification given by the client. Since
the client satisfaction is very important for any project.

22. If there are a lot of bugs to be fixed, which one would you resolve first ?

As a tester only find out the bugs. We can’t fix the bugs. Developer will be fix the
bugs.

Tester set the severity and priority of bugs. Communicate with developer and lead to
identify which bugs need to be fixed first based on the business requirement
document. Otherwise it is always defined in project management planning documents
which bugs needs to be fixed on priority.

23. How can you test the web application in manually?

In the web application testing in manually, mainly we will concentrate the 6 areas.

1. Functionality testing:

Links: check for all the links in the website

Internal Links
External Links
All mail Links
Broken Links.

Forms:
 Field level validation : check the length, special characters, numerical characters,
etc.

Functional check: check the create, delete, edit, and view are working or not.
Error Handling for wrong inputs or action: check the error message displaying or
not.
Optional and Mandatory fields: mandatory field should not be left blank.
Optional should allow the user to skip the field.

Cookies: check the cookies are enabled. web site use cookies to simulate a
continues connection to that site.
Data integrity: should not be any missing or wrong data in the database.

2. Usability testing:

Navigation:

checking the application navigation is proper through Tab.

Navigation through mouse.
Main features accessible from main/home page
Any hot keys, control keys to access menus.

Content:

Check the spelling errors.

General appearance: page appearance ,colour, size, font, frames, consistent design.

3. Server side interface:

Verify that communication is done correctly.

Web server- Application server- Database server and vice versa.

4. Client side compatibility:

Check the application running in different operating system and different

browsers. Check the printing.

5. Performance:

Connection speed/performance: check the application run time performance speed

in different connection speed.

Load: checking the application more load or less load (users).

Stress: Run the application all in low condition.

6. Security:
 Valid and Invalid Login
Limit defined for the number of trails.
No access to edit scripts on the server without authorization.
verify log files are maintained to store the information for traceability.

24. Why the Compatibility Testing is needed? Explain this with real time example ?

In compatibility testing we have to validate the application under different OS and

browsers. two types of compatibility.

Forward Compatibility: Application developed under one OS ,should works fine on

future version. Ex: App developed windows95 means it should be worked
windows2000.

Backward Compatibility: Application developed under one OS ,should works fine

on Past version. Ex: App developed windows7 means it should be worked
windows2000.

25. What is AGILE?

Agile is nothing but a process. In this process we will perform the complete software
development life cycle within a short period.

In this agile process we have a lot of methodology. Scrum, extreme programming, agile
data method etc.

In our company we followed scrum methodology.

26. what are the advantages of agile process?

Team work (Communication approach)

Quick feedback is main advantages in agile process.
Within in a short period we will deliver the good quality product.

Disadvantages: low documentation.

27. What is scrum master or scrum methodology?

Scum is nothing but it is one of the agile process methodology. Scum is an iterative
incremental framework for managing projects. Focuses on managing system with
changing requirements. In this methodology we will follow the time terminology. It’s
called an iteration. Iteration is nothing but set of time period.
Basically in scrum iteration will be 1-4 week.
Scrum size should be 10-12 members.
28. what is your scrum process or role of a agile tester or agile process?

In our Agile process we followed scrum methodology. In this scrum process we will
follow the sprint back log documentation. In scrum we have a iteration planning
meeting. At the beginning of the IPM we will fix the our iteration size is 2weeks.
When the iteration will start we will break down the requirements and we will follow
the stories. In this IPM we will discuss the estimation of stories. (Estimation is
nothing but time duration of finishing the stories).once we fix the stories in IPM it’s
constant we don’t change the stories in that iteration period. In this iteration period
daily we will conduct the Stand Up meeting. In this meeting we will discuss the
mainly three things

1. what did you do yesterday

2. what will you do today
3. any issues or any disadvantages in your way.

When the stories estimation done , as a tester I can write the test cases for that stories.
Once the stories deployed in test environment I will execute the test cases and find
out the bugs. If any failure I will raise the bug in bug tracking tool and assign the
developer. Once stories passed I can sign off the stories and I can inform the business
representative for a quick check. For end of the iteration we have a Show Case
meeting and after the show case meeting we have a Retrospective meeting. In mean
time we have a any doubt we will conduct the Huddle. This is our agile process.

29. How do you communicate with developer in case you a bug?

Double check the, whether it is a bug or not. Check the requirement how it’s working.
What is the flow of that requirement, what is the expected result of that requirement.
Then I will check the my test cases for that requirement. Still it’s bug is coming I will
raise the bug in bug tracking tool and I will try to explain the developer , what I have
tested what I am getting. This way I will communicate the developer.

30. What are the advantages and disadvantages of manual testing?

Manual testing is preferable for product with short period.

Manual testing we will give the depth in the quality. We will test the each
functionality step by step.

Good documentation in each functionality.

Disadvantages:

It is time taking process

Need a More resources.

31. Why you need automation testing tool? Benefits of automation testing tool?

Fast: automated tools run tests significantly faster than human users.

Reliable : tests perform exactly the same operations each time they are run.
Eliminating human errors.

Reusability : you can reuse tests on different versions of an application. Even if the
user interface changes

Cost reduction: manual testing man power is required more ,automation man power
can be less.

Long term project automation tool is better.

We can run the more tests in less time with few resources.

Regression testing is easy compare to manual testing.

Disadvantages Automation Tools:

Knowledge is required to write the automation test scripts.

Debugging the test script is major issues.

Test maintenance is costly in case of play back method.

Maintenance of test data files is difficult.

32. How do you choose the automation tool in new project?

Check the whether it is a web base project or windows base project.

Compatibility: check the development languages is supporting automation tool or not.

Environment support: Operating system is supporting our automation tool or not.

User friendly or not

Finally we will check the budget vice open source or pay tool .

33. Explain about selenium tool?

Or
 Do you have any experience of Selenium? If so, what are the benefits of using such a
tool?

Selenium is nothing but a web application tool. It is test the websites only. It is used to
only a functionality of the testing. In this selenium tool we can’t do the any performance
test.

Selenium is a portable software testing framework for web application. Selenium is a

open source software.

Selenium Tool Advantages:

You can able to do multi browser testing.

You can handle to different languages.

Selenium configuration run the different operating system.

Selenium consist of Different types:

Selenium IDE (Integrated Development Environment)

Selenium RC

Selenium Core

Selenium Grid

Selenium IDE: selenium IDE is nothing but a Firefox plug-in . Selenium IDE is works
only for Firefox. It is also called recorder. Operation whatever you perform in the
website that can only be executed. We can’t add the any condition. IDE default code is
HTML. You can export the different languages but you can’t run code in different
languages. You can run code in HTML language .Integrate the more then different
languages in this tool.

Selenium IDE will intelligently find the positions.

Selenium IDE mainly perform three operations

1. Action: click, type

2. Assessors: declare the variables.
3. Asserts : checking something.

Selenium IDE Commands:

Assert Text Present : text is present or not in whole website

Assert Text: text is present in particular position.

Assert Element Present: verify the images, buttons, fields

Verify

Wait

Store

Assert and verify differences:

Assert: immediately show the error and stop the operation

Verify: if any error is their perform the whole operation and end it fill show the failure.

34. How to use selenium for performance testing ?

Selenium is nothing but a web application tool. It is test the websites only. It is used to
only a functionality of the testing. In this selenium tool we can’t do the any performance
test.

35. What are the locating strategy?

Locating: Locating strategy.

1. By ID : When will you execute selenium it will find out the first functional ID

Ex: //*[id=’s f’]/span.

2. By X path:

Developer didn’t use id then how can you locate the element

3. By name : class, type

//span[@class=’gbt’]

If id’s name same in different elements

I can check the different class name or their

4. By Css: Cascading style sheet

in the locating path double slash // define the parent path and single slash / define the
child path

36. What you do if a page doesn’t have ID or name attribute?

 If the page source does not have an ID or name attribute you have no choice but to use
an Xpath or DOM locator

37. Disadvantages of Selenium IDE?

Selenium IDE just recorder and play back tool. In this tool you can’t use the
conditions.
Selenium IDE can run the only fire fox browser only.
Selenium IDE operation code ,we can format the different languages but we can’t
execute the code in different languages.
Multi browser testing not possible in selenium IDE.
Reporting not possible.
Database connectivity not possible.
Screen shot capture future is not available.

38. What is the differences between Selenium IDE and Selenium RC?

Multi browser testing is possible in selenium RC.

Conditions possible in selenium RC.

We can execute the code in different languages.

Reporting possible.

Database connectivity possible.

Screen shot capture future is available in selenium RC.

39. Can you tell me about your selenium setup and execution process?

Or

What is your test setup?

Or

What is your selenium frame work?

Or

Briefly explain how you will do end to end testing?

Or

What is your experience of automated build, testing frameworks and one-touch

deployment?

In automation testing we used Selenium RC. In selenium RC we used Eclipse client tool
for write the java code. In eclipse we have a three packages.
1. Functional package: where we have all the functional tests in inside. That means we
will execute the individual test stories one by one functional package.

2. Properties package: where we declare all the parameters which are use in our test.

3. Test suite package: test suite consist of all the group of individual tests. This test suite
is useful for regression testing purpose.

4. Top up that we have a continuous integration process in our company which does
automatic regression testing.

This is our test set up or selenium set up or selenium frame work or end to end testing.

40. Do you have experience of Continuous Integration? CI tools?

Yes. Automatic regression testing purpose We can use the continuous integration
process. In this CI concept we will use the Repository tool. It is nothing but a central
database.

In the repository tool ,As a tester I can add the stories in automation test suite.

Whenever developer run the code in his local machine, it’s passed, put it the code in
dev environment and pass the test environment repository tool. In the test
environment code is passed it will trigger our automation suite and send the result
automatically mail by developer and tester. In this process developer code failed,
build will be fail automatically and it’s never touch the automation test suite code.
This is our build pipeline or continuous integration process.

41. Which test framework you used for selenium testing?

Junit 3 frame work we used in our selenium testing.

42. What are the challenges you faced while using selenium?

•Dealing with pop-up windows

• Testing dynamic text or content
• How to go about testing Flash
• Capturing screen shots, either to file or in some form of report
• Iteration of the test case, running it repeatedly with some minor change
• Data Driven Testing, using suites of pre-cooked data or generating it on the fly
• Generating useful test status reports
• Setting up Remote Control

43. What you say about the flexibility of Selenium test suite?
Ans. Selenium testing suite is highly flexible. There are multiple ways to add
 functionality to Selenium framework to customize test automation. As compared to
other test automation tools, it is Selenium’s strongest characteristic. Selenium Remote
Control support for multiple programming and scripting languages allows the test
automation engineer to build any logic they need into their automated testing and to
use a preferred programming or scripting language of one’s choice. Also, the
Selenium testing suite is an open source project where code can be modified and
enhancements can be submitted for contribution.

44. Where you will store the your automation test script?

We can store the automation test script in Repository tool.

All our automation test script run in virtual machine.

45. How to start the selenium server from your language class?

In the project references libraries folder we can add the selenium jar files. Then after
in command prompt we can run the selenium server command .

Java –jar selenium-server.jar.

46) What is their latest project and explain in detail (they can hide any confidential
information)?

Molton Brown is one of the leading company in fashion retailer based in UK. Recently
website is redesigned and added more features to enhance and attract web customers while
shopping online. So my role to ensure each and every functionality of newly added web
components and already existed links functioning properly or not, And that should satisfy
customer’s online shopping. Aim of this project is to provide consistent, integrated internet
applications that are intuitive, dependable and easy to use for all of its corporate customers. A
New Admin Center Application is being developed for theMolton Inc Chase investment bank
to improve the existing process of creating and maintaining new client information.

47) How the project has helped the client in enhancing/staring his business?

As a global technology company, our client is a market leader in employee management and
security solutions, offering their customers a range of Time and Attendance software systems.
They currently have around of 30000 customers worldwide; including some of the leading
fashion retails companies in the UK.  They are based in UK & Europe and have ambitious
growth plans, aiming to double in size in the next few years. So, the project is to provide
consistent, integrated internet applications that are intuitive, dependable and easy to use for
all its corporate customers.
48) What’s your role? 

In our agile process we followed scrum methodology. In this scrum process we will follow
the sprint back log documentation. In scrum we have an iteration planning meeting. At the
beginning of the IPM we will fix the iteration size of 2weeks. When the iteration starts we
will break down the requirements and we will follow the stories. In this IPM we will discuss
the estimation of stories. Once we fix the stories in IPM its constant we don’t change the
stories in that iteration period. In this iteration period daily we will conduct the Stand Up
meeting. In this meeting we will discuss the mainly three things

4. what did you do yesterday

5. what will you do today
6. Any issues or any disadvantages in your way.

When the stories estimation done, As a tester I can write the test cases for that stories.
Once the stories deployed in test environment, I will execute the test cases and find
out the bugs. If any failure I will raise the bug in bug tracking tool and assign to
developer. Once stories passed I can sign off the stories and I can inform the business
representative for a quick check. For end of the iteration we have a Show Case
meeting and after the show case meeting. We have a Retrospective meeting. In mean
time we have any doubt we will conduct the Huddle. This is our agile process.

49) What you  have contributed to the project?

During the project, I was responsible for quality assurance of HTML templates (with a focus
on cross-browser and mobile based testing), website content and navigation (with a focus on
adherence to agreed information architecture) and functional testing of forms and other user
inputs.
And I used a various software tools and developed numerous manual and automated test
scripts which greatly assisted the organisation in delivering robust, user-friendly products. As
an employee I was punctual, analytical and dedicated. I was an excellent eye for detail and a
solid understanding of testing from both a user and technical perspective.

50) What did you learn (new things) from the latest project?

My last project was an excellent learning opportunity and I developed my skills and
experience in numerous different ways. While I already had strong software tool skills, I
didn’t have any previous experience of kentico access. When my employer introduced a new
content management system which used Access they gave me the opportunity to undertake
additional training so as to be able to work effectively with this. I was then able to put this
training into practice on a day-to-day basis and I am now extremely adept at using the
package. I also learned a great deal about handling developer tool. My previous roles were
not testing come developer so it was great to have the chance to develop this area of my
experience. 

51) . What are the issues faced by the candidate and how did he overcome those issues?
I faced some difficulties like bug raised at end of the current iteration process and we don’t
have the sufficient time to fix the bug in the same iteration before handover to end user. To
resolve this issue we organised a sprint meeting and decided to fix it in the next iteration as a
priority. And we successfully hand over the work to end user without having bugs in it.

While executing the automation test scripts I face some of these challenges

Dealing with pop-up windows

• Testing dynamic text or content
• How to go about testing Flash
• Capturing screen shots, either to file or in some form of report
• Iteration of the test case, running it repeatedly with some minor change
• Data Driven Testing, using suites of pre-cooked data or generating it on the fly
• Generating useful test status reports

52) Why should I hire you?

I think this is the great opportunity for me to work with your company. And am well
disciplined and hardworking person & moreover this designation comes under my field of
interest so I think I can turn in your company’s growth. And I have all the qualities which
you are mentioned in the job description. And I want to be an asset to your company

53) What are your strengths?

My strengths are my positive attitude and my self confidence. In any difficult situations or
any challenges my positive outlook helps me a lot to reach a successful solution. And
moreover my self confidence and dedication towards work makes me more confident and it
increase my strength.

54) What is your weakness?

When I am working on a project I just don’t want meet deadlines rather I prefer to complete
my project well ahead schedule. Being organized wasn’t my strongest point but I
implemented a time management system that really helped my organization skills. I have
learned to make my perfectionism work to my advantage at work and am excellent at
meeting deadlines and with all attention to detail I know my work is correct.

55) Where do you see yourself in next five years?

In next five years I hope to be working with an employer in a increasingly responsible position , that
enables me to utilize my skills and talent at work with my colleagues to solve important problems
and more over I see myself taking a new exciting challenges in a enjoyable environment & hopefully
this will be with your company.
 57) What did you learn (new things) from the latest project?

My last project was an excellent learning opportunity and I developed my skills and
experience in numerous different ways. While I already had strong software tool skills, I
didn’t have any previous experience of kentico access. When my employer introduced a new
content management system which used Access they gave me the opportunity to undertake
additional training so as to be able to work effectively with this. I was then able to put this
training into practice on a day-to-day basis and I am now extremely adept at using the
package. I also learned a great deal about handling developer tool. My previous roles were
not testing come developer so it was great to have the chance to develop this area of my
experience. 

58) What motivates you in your job?

I am motivated by taking challenge of difficult tasks and projects. My previous manager gave
me more and more responsibility as I proved myself, I found this very motivating.

It is important for me to meet the project deadlines and team targets. I give them the best
service and when I exceed my team expectations or getting positive feedback it motivates me
a lot.

I like to know that I am growing as an employee. Learning and using new skills is a big
motivator for me.

59) What interests you most about this job?

I want to learn and take new exciting challenges from every new opportunity and develop my
skills in a various ways. I consider this strategy of development one of my key skills and I
would like to be able to use it to the fullest in developing strategies for an organisation. I like
challenges of adapting my approach to suit the individual and the situation. And hopefully I
can see this positive field in this role that’s why I am pretty interested in this job.

60) Describe your ideal job

My ideal job is one where my knowledge and skills are kept together and execute for good
use. A job where I will learn and grow as a person and an employee and where I am given
challenges that test my potential.
I believe a job is what you make of it. Each position and company has a unique characteristic
that gives meaning and value to that job. If you work hard and make the most of the
opportunities given, you will find job satisfaction. I am enthusiastic about a position that
allows me to learn and grow and to make a positive and meaningful contribution.

61) How have you enriched your current job?

My Test team had to meet a deadline of a build release launch in the market and I
volunteered to help out with preparing and developing the Test data and scripts in both in
manual and automation types. I worked overtime to successfully complete the project before
the deadline. My manager was very pleased with my work and I received a commendation
from the Test Director.

62) What do you like least about your current or last job?

There was very little opportunity for me to use my skills and initiative. I regard this as one of
my strengths and found it frustrating that I was unable to get past the organisation of such a
big company to implement any improvements. That is why I am enthusiastic about working
for a smaller company like this which I know encourages employees to use their initiative.

63) How would your co-workers describe you?

My colleagues consider me to be hard working and punctual at doing things and easy going
friendly with team members. In fact, the other team members often thanked me for the extra
hours I put in my project.

I know that I was initially considered intolerant if I felt they were not putting in the same
amount of effort as I was. I realized it was better to encourage them to meet our deadlines by
offering help where needed. This has worked much better for all of us.

64) Are you better working in a team or working alone?

I am a team player. I get along with team members very well. As far as the working is
concerned, I can be equally productive in team or working alone.

65) What do you like about a Manager? And what don’t you like?

The best thing I like about a Manager is that the Manager should be able to coordinate with
the other teams so that we can get the updated documents, for example, updated requirements
documents right away. A Manager who can efficiently in distributes the work to the team,
without being biased and easily accessible and protective to his team for the right cause. As
far as “what I don’t like” is concerned, I don’t like a manager who keeps coming to desk 10
times a day to check my work even if it is just a regular work. Once the responsibility is
given, the team member should be trusted and let his work done.

 66) Why do you like this job?

I like this job, because it is process oriented. Meaning that I get an opportunity to work from
analyzing the requirement documents to writing test plans, test cases, testing the application,
logging defects, retesting, preparing reports and finally testing in production as well.
Therefore, I am involved from the very beginning to the end of the software development life
cycle (SDLC) process. I like this.
Another reason is I like to find defects. I enjoy logging defects. The more defects I find, the
happier I am.

67) What is the biggest bug you have ever found?

Well, there are many big defects I have found in various projects. For example, in the last
project, on a page, there was a button called “More Information”. Once the user clicked that
button, the system would open a new window (pop up).
We could close the new window in 3 ways:
-By clicking X at the top right corner of the page
-By clicking “Close” button on the page
-By pressing combination keys (Alt+F4) on the key board
Although the combination key (Alt+F4) was not mentioned in the test case, I just wanted to
try how the application reacts when Alt+F4 is pressed. Then I pressed Alt+F4. The result was
a disaster-the application crashed (broke). The application disappeared from the computer
monitor. Since it was the last day of testing for us, it brought chaos in our Managers, Leads
and the whole teams. Finally, the developers disabled Alt+F4 as a temporary solution and the
application went into production.

68) As a QA Tester, can you tell me the situation when you felt the most proud of it?

When I find the defect that normally others don’t find, then I feel very proud. For example,
there were situations where I found bugs that crashed the whole system at the end of testing
phase. I tried the scenarios where the scenarios were NOT mentioned in the test cases. For
example, we can close the windows by clicking X on the page, with “Close” button and so
on. But there is another way that you can close the window, by pressing Alt+F4 on the
keyboard. Not many testers test this scenario. I have done this in my last two projects. Both
the time, the application crashed which became a big issue. I felt proud.

  69) What problems did you face in the past? How did you solve it?

I had many problems while testing applications in the past.

As far as I remember one of them (then describe one of them from below), this was the
scenario:
It was a web-based application. I was working on a module called “Transaction Summary”.
There was “Submit” button on that page. After entering data in the all the fields, for example,
First Name, Last Name, Social Security Number, Date of Birth and so on, I clicked the
Submit button. Once I clicked Submit button, an error page displayed, “Page cannot be
found…”. Since it was a critical defect, I immediately informed the Test Lead. There was a
chaos in the room. All the developers, Database Administrators and Testers gathered in my
cube (room). No body could tell exactly what was wrong with it. Finally, one smart guy
checked into the database and found out that one of the files in the database was closed. The
status of all the files should be in the open status. Once the status of the closed file was put in
the “open” status, the application worked fine.

70) Can you work under pressure?

Of course I can work under pressure. In fact more the pressure more I motivate myself to
do more hard work. Actually pressure is for those who take their job as earnings. And a
person like me who enjoys the job, take it as a challenge and feel good when working
under pressure. So I don't think working under pressure will be any problem at all. But of
course the pressure must be optimum as "excess of anything is good for nothing".
Actually if there is no pressure then there is no challenge, means person completing the
task will not have the happiness which probably might be there if he does that in a
challenging environment.

71) What is their latest project and explain in detail (they can hide any confidential
information)?

Blue Inc is one of the leading companies in fashion retailer based in UK. Recently website is
redesigned and added more features to enhance and attract web customers while shopping
online. So my role to ensure each and every functionality of newly added web components
and already existed links functioning properly or not, And that should satisfy customer’s
online shopping. Aim of this project is to provide consistent, integrated internet applications
that are intuitive, dependable and easy to use for all of its corporate customers. A New Admin
Center Application is being developed for the Blue Inc Chase investment bank to improve the
existing process of creating and maintaining new client information.

72) What you  have contributed to the project

During the project, I was responsible for quality assurance of HTML templates (with a focus
on cross-browser and mobile based testing), website content and navigation (with a focus on
adherence to agreed information architecture) and functional testing of forms and other user
inputs.
And I used a various software tools and developed numerous manual and automated test
scripts which greatly assisted the organisation in delivering robust, user-friendly products. As
an employee I was punctual, analytical and dedicated. I was an excellent eye for detail and a
solid understanding of testing from both a user and technical perspective.