What is desk check in testing?

Desk checking is an informal manual test that programmers can use to verify coding and algorithm logic before a program launch. This enables them to spot errors that might prevent a program from working as it should.

How do you use a desk check?

Desk check is performed manually by walking through every line in a pseudo-code to identify the bugs in logic and to ensure if the algorithm works as intended. It is performed on an algorithm code using tables with columns as line number, value of variables, conditions if applicable, input-output and result expected.

What is a desk check in agile?

A Desk Check is a practice to be used for verification when the pair of developers believe the development is complete. In the list below we see verifications such as: Were unit and acceptance tests implemented? Did you invite someone to review your code?

What is the desk check review?

A desk check is an informal review where the author distributes a work product to peers for reviews and comments. A walkthrough is an informal review mee”ng, moderated by the author of a work product. An inspecfion is a formal review mee”ng, guided by a moderator.

What is the purpose of a desk check?

A desk check is an informal non-computerized or manual process for verifying the programming and logic of an algorithm before the program is launched. A desk check helps programmers to find bugs and errors which would prevent the application from functioning properly.

What is manual support testing?

What Is Manual Testing? Manual testing is the process in which QA analysts execute tests one-by-one in an individual manner. The purpose of manual testing is to catch bugs and feature issues before a software application goes live. When manually testing, the tester validates the key features of a software application.

What is the difference between desk checking and inspection?

An inspection or walkthrough is an improvement over the older desk-checking process (the process of a programmer reading his or her own program before testing it). Inspections and walkthroughs are more effective, again because people other than the program’s author are involved in the process.

How do I write pseudocode?

Rules of writing pseudocode

  1. Always capitalize the initial word (often one of the main 6 constructs).
  2. Have only one statement per line.
  3. Indent to show hierarchy, improve readability, and show nested constructs.
  4. Always end multiline sections using any of the END keywords (ENDIF, ENDWHILE, etc.).