FAQ - Manual ( 11 to 20 )

11. When a bug status will be changed to "DEFERRED”, by the developer? What might b the situations to change the status to deferred? Pls explain with an example

When a bug is not of high "priority" and it’s not going to cause any serious failure as such on customer's side i.e. it’s of low "severity" also, then the developer can change the bug status to "deferred”. For eg, while coding the GUI part of the application, developer has provided menus to navigate to other pages but he forgot to provide “NEXT" button on home page, which is a part of the requirement then he can defer it for later modification.

12. What report u generate after completing testing?

* Test Result Record

* Test summary report

* Defect report

* Release plan and Test review record

13. On what basis u design the test cases?

To design test cases there is templates for writing test cases. In the Templates there is serial number; action to be performed, test data, expected result, actual result and defect id has to be given. To design test case we have to provide each of these data for each function keys. These function keys are derived from FS which also derive from SRS.

14. Test cases for car and cell phone?

Test cases for car is

* To open the door open correctly

* To correctly start the car by using key

* To correctly move the steering

* Incorrectly move the steering

* Follow the traffic rules correctly

* Follow the traffic rules incorrectly

Test cases for cell phone

* To open the lock by given the correct security code

* Give incorrect security code

* To search the correct number for making call

* To search the incorrect number for making call

* To find the messages

15. What is difference between Client-Server and Web based architecture?

Client server is a 2-tier application. In this, front end or client is connected to’ Data base server' through 'Data Source Name’; front end is the monitoring level.

Web based Architecture is a 3-tier application. In this, browser is connected to web server through TCP/IP and web server is connected to Data base server, browser is the monitoring level.

16. Test scripts in the Manual testing ?

Test Script means test case documents in the case of manual testing. If we go for automated testing Test script means code of the test. In any mode of testing (i.e. in both Automated and Manual) first testers will prepare Test case index. It contains only all possible test case labels. Then testing people go for detailed test case writing. Then they prepare test procedure and test data.

17. At what stage of the life cycle does testing begin?

In life cycle testing begins right from after completion of coding that is UNIT TESTING

That comes under WHITE BOX TESTING after that integration testing after that SYSTEM TESTING i.e. is BLACK BOX TESTING

18. On what basis we’ll prepare the test cases.

SRS describes the requirements of the SW system. We use SRS document as a basis to write Testcases. We use tractability matrix as basis to decide whether the designed no. of test cases are enough. Requirement Traceability matrix is very important in deciding number of test cases and also in review process of test cases.

19. List five words that best describe ur strengths

Hardworking, quick learner, team player, stable and reliable.

20. Your exposure to GUI testing

Overall look of the web page, color requirements, content alignment, logo appearance and size of the object appearing on the web page etc.

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.