Amazon offers

Do you know which is the first bug found


The invention of the term "bug" is often erroneously attributed to Grace Hopper, who publicized the cause of a malfunction in an early electromechanical computer. 

A typical version of the story is given by this quote:
“
In 1946, when Hopper was released from active duty, she joined the Harvard Faculty at the Computation Laboratory where she continued her work on the Mark-II and Mark-III (The Harvard Mark II was an electromechanical computer built at Harvard University under the direction of Howard and was finished in 1947. It was financed by the United States navy). Operators traced an error in the Mark II to a moth trapped in a relay, coining the term bug. This bug was carefully removed and taped to the log book. Stemming from the first bug, today we call errors or glitch's in a program a bug.
”
Hopper was not actually the one who found the insect, as she readily acknowledged. The date in the log book was 9 September 1947, although sometimes erroneously reported as 1945. The operators who did find it, including William "Bill" Burke, later of the Naval Weapons Laboratory, Dahlgren, Virginia were familiar with the engineering term and, amused, kept the insect with the notation "First actual case of bug being found." Hopper loved to recount the story. This log book is on display in the Smithsonian National Museum of American History, complete with moth attached.
While it is certain that the Harvard Mark II operators did not coin the term "bug", it has been suggested that they did coin the related term, "debug”. Even this is unlikely, since the Oxford English Dictionary entry for "debug" contains a use of "debugging" in the context of air-plane engines in 1945.

See the first bug picture 








Comments

Post a Comment

Popular posts from this blog

Input Data Validation

Every web application is expected have at least one submit form. Data entered in form is transferred as input to database or to any other application and will decide the output. So, input data plays a very important role in retrieving the output data. Such data needs to be validated by the code. And tester has the responsibility of validating such data. At this point tester thinks about how can the validations be done and what type of data should be provided to validate the input field. Test data needs to be created and passed to the form through the automation tool or manually. Here are few steps or guide lines to validate the data. Let’s consider a sample form which acts as input to signing in as new member in a social networking site like facebook. It contains different types of input fields – Numeric, String, Alpha Numeric, date, preset values (from drop downs or check boxes), file uploads and Email addresses. Name: String input field Password : Alphanumeri
Read More

How to test search functionality

Every web application by default will contain search feature in it. Many search engines’ main functionality is search feature. The parameters to be considered while developing this feature or testing this feature are not limited. There are many factors which should be looked in when checking the coverage and usability of the search text box in the application. Preparation before testing the search functionality 1.        Note down the valid input details for the search feature. 2.        Find out the minimum and maximum range. 3.        Find out the depth of the search – document search, word in a document, image search 4.        Should document search display the size of the document also? Similarly for image? 5.        Any advanced search features like document or image type selection to refine the search are available? 6.        General set of input which can be given are a.        A-Z b.       a-z c.        0-9 d.       {      [              (       
Read More

Scrum Methodology - Quick Info

Image
It is one of the unique methodologies of agile methodology. Scrum  It is an   iterative, incremental   framework for project management . It   is a loose set of guidelines that govern the development process of a product, from its design stages to its completion. It aims to cure some common failures of the typical development process like a. chaos due to changing requirements, unrealistic estimates of time, cost and quality of the product. Meetings 1.      Daily Scrum meeting or daily stand up meeting: agenda:  what is done, what is planned for today, what are the problems in accomplishing the goal? 2.      Sprint planning meeting : Before each sprint cycle (7-30 days)starts, prepare sprint backlog, timelines, 3.      Sprint review meeting: done at the end of sprint cycle, review work completed and not completed, demo the work completed, do not demo incomplete work, 4 hour time will be allocated. 4.      Sprint retrospective meeting: done at the end o
Read More