FAQ - Manual ( 31 to 40 )

31. How many test cases can you write an average for a day?

There is no measurement for writing the test cases avg for a day. That depends on functionality. If the functionality is critical we can write just 5 to 10 test cases otherwise

We can write 60 to 70. In this way the average for day is 30-35.

32. What does buddy testing mean?

Due to lack of time for testing, test engineer grouped with programmer to conduct testing as early as possible. Buddy means a group with programmer and tester. It is a type of ad-hoc testing

33. What are the difference bug, error, and defect?

Bug : Discrepancy in the application functionality

Error : Mistakes in coding

Defect : Deviations from the requirements

34. When the relationship occurs between tester and developer?

Developer is the one who sends the application to the tester by doing all the necessary code in the application and sends the marshal id to the tester. The tester is the one who gives all the input/output and checks whether he is getting required output or not. A developer is the one who works on inside interfacing where as the tester is the one who works on outside interfacing

35. Write 5 negative test cases for pen?

1. Throw the pen at a Wall and try Write in again.

2. Hold the Pen in the upward direction for 5 mins and try writing in.

3. Do not use the pen for 10 days and then try writing up.

4. Throw the pen in the water and then write up again.

5. Expose the pen to the heavy weather conditions and try writing up with the same.

36. What are the contents of FRS?

Function Behaviors Requirements (Outputs) of the System that is defined.

Specification (How, What, When, Where, and Way it Behaviors.

Function Requirement Specification.

This is a Document, which contains the Functional behavior of the system or a feature. This document is also known as EBS External Behaviors Specification-Document or EFS External Function Specification

37. Give me some example for high severity and low priority defect?

High severity:

Eg: Calculation bugs

Low priority:

Returning float with single decimal point with rounding the value instead of two decimal points can be treated as low severity.

Eg: Expected: 77.77

Actual: 77.8

38. What is the Difference between Web Application testing and Client Server testing ?

In both Tests we perform Load and Performance Testing. Testing the application in intranet (without browser) is an example for client-server. (The company firewalls for the Server is not open to outside world. Outside people cannot access the application.) So there will be if limited number of people using that application.

Testing an application in Internet using browser is called web testing. The application which is accessible by numerous numbers around the world (World wide web). So testing web application, apart from the above said two testing there are many other testing to be done depending on the type of web application we are testing. If it is a secured application (like banking site-we go for security testing etc.) If it is a commerce testing application we go for Usability Testing

39. Explain about Bug life cycle?

1) Tester->2) open defect->3) send to developer 4)->if accepted moves to step5 else send the bug to tester gain 5) Fixed by developer->6) regression testing->7) no problem in Built and signoff 8)->if problem in built reopen the issue Send to step3

40. What are the common defects revealed in Functionality Testing?

Page not found (Error 404)

Server not found

Page Errors

FAQ - Manual ( 01 to 10 )

1. How do u start testing a module

First once the module is given, the modules flow has to be first understood, for that we need to thoroughly go through the module by entering the values and understanding the module.

Secondly once the flow of the module is understood, we need to create an test frame work.

Then we will design the test cases and then we will start executing the test cases.

2. Difference between severity and priority?

The word "priority" is associated with scheduling, and the word "severity" is associated with standards. "Priority" means something is afforded or deserves prior attention; a precedence established by urgency or order of or importance.

Severity is the state or quality of being severe; severe implies adherence to rigorous standards or high principles and often suggests harshness; severe is marked by or requires strict adherence to rigorous standards or high principles. For example, a severe code of behavior.

3. What is a bug life cycle??

* UNCONFIRMED - This bug has recently been added to the database. Nobody has validated that this bug is true. Users who have the "can confirm" permission set may confirm this bug, changing its state to NEW. Or, it may be directly resolved and marked RESOLVED.

* NEW - This bug has recently been added to the assignee's list of bugs and must be processed. Bugs in this state may be accepted, and become ASSIGNED, passed on to someone else, and remain NEW, or resolved and marked RESOLVED.

* ASSIGNED - This bug is not yet resolved, but is assigned to the proper person. From here bugs can be given to another person and become NEW, or resolved and become RESOLVED.

* NEEDINFO - More information from the reporter is needed to proceed further in fixing this bug.

* REOPENED - This bug was once resolved, but the resolution was deemed incorrect. For example, a WORKSFORME bug is REOPENED when more information shows up and the bug is now reproducible. From here bugs are either marked ASSIGNED or RESOLVED.

* RESOLVED - A resolution has been taken, and it is awaiting verification by QA. From here bugs are either re-opened and become REOPENED, are marked VERIFIED, or are closed for good and marked CLOSED.

* VERIFIED - QA has looked at the bug and the resolution and agrees that the appropriate resolution has been taken. Bugs remain in this state until the product they were reported against actually ships, at which point they become CLOSED.

* CLOSED - The bug is considered dead, the resolution is correct. Any zombie bugs who choose to walk the earth again must do so by becoming REOPENED.

4. Difference between Critical and show stopper severity bug?

Critical Bug is a defect in any functionality; still the system can be preceded with other functionalities whereas if there is a show stopper bug, the system cannot be preceded from that point.

5. Stages of a bug?

1) Open stage : A defect originated by a tester
2) Assign : Raised defect assigned to Developer
3) Resolved stage : Developer provides code fix for the bug and make it resolved

4) Closed stage : Tester re-tests the bug and closes it, if it’s working. Otherwise he will re-open the defect and it will go back to stage 1.

6. Difference between web server and client server?

Web server - A computer that delivers (serves up) Web pages. Every Web server has an IP address and possibly a domain name

Client server - A network architecture in which each computer or process on the network is either a client or a server. Servers are powerful computers or processes dedicated to managing disk drives (file servers), printers (print servers), or network traffic (network servers). Clients are PCs or workstations on which users run applications. Clients rely on servers for resources, such as files, devices, and even processing power.

7. Difference between SRS and Use cases?

SRS – Software Requirement Specification. It acts as a bible for the requirements of the whole system.

Use Cases is the pictorial representation of the whole functionality of the system.

8. Difference between Load Testing and performance testing.

The Performance testing is something where we find the response time of the application, Look out the Bottlenecks & Tune it.

A Load testing is done once if the functional and Performance testing is up and done to check the minimum and maximum load the Application can handle.

9. What is the role of tester in a Company ?

* Design Test cases.

* Execute Test cases.

* Bug or Defect Tracking.

* Test Report.

* Co-ordination to Prepare Test Plan (Optional).

10. What might be the reasons for changing the status of a bug to "NOT A BUG“

The bug might be occurred due to some errors in the test cases or due to some errors that occurred during the execution of test cases. These can be the reasons for changing the status of a bug to not a bug.