Demo web application

Demo web application - Journey Planner

---

This is a simple web application. You should enter the total distance to travel, the average travel speed and the time to travel every 24 hours. Then click on the Calculate Travel Days button.
- If any data entered by you is invalid, you will get an error message in red color.
- If the data you entered is valid, you will get the number of travel days rounded off to 4 decimal places and in black color.
- If you click the Reset Values button, you will empty the distance to travel and average travel speed values and reset the time to travel every 24 hours to 1 hour.
Note: This web app needs a HTML5 and JavaScript-enabled browser in order to display and function correctly.

---

Enter the distance to travel (max. 10 digits with decimals):         mile(s)

Enter the average travel speed (max. 10 digits with decimals):  mile(s)/ hour

Select the time to travel every 24 hours:  15 minutes30 minutes45 minutes 1 hour2 hours3 hours4 hours5 hours 6 hours7 hours8 hours9 hours10 hours 11 hours12 hours13 hours14 hours15 hours 16 hours17 hours18 hours19 hours20 hours 21 hours22 hours23 hours24 hours (non-stop)

---

---

Free Software Testing Tutorials

Several people who are starting out in software testing have inquired about software testing tutorials. Here is the complete list of free software testing tutorials that you can use to train yourself in the concepts of software testing. The link is:

Software Testing Tutorials

You should view these software testing training videos in the following order:

1. What is software testing? Why test software?
2. Waterfall SDLC and V Model in testing
3. Requirements analysis
4. Software test strategy
5. Agile test strategy and Agile test plan
6. Test cases
7. Writing test cases effectively
8. Test data
9. System testing
10. Regression testing
11. Requirements Traceability Matrix
12. Testing reports
13. Bug reporting
14. Test status report
15. Software tester roles and responsibilities
16. Equivalence Partitioning and Boundary Value Analysis
17. Decision Table Testing
18. Use Case Testing
19. State Transition Testing
20. How to design Test Ideas quickly
21. How to get Domain Knowledge
22. How to Test Software without Requirements
23. Top tips to get software testing jobs
24. Building software testing skills
25. How to become Software Testing Expert
26. Test Estimation with formula example and Questions and Answers
27. Test Lead Interview Questions And Answers
28. How to Identify Risks?
29. Risk Management in Software Projects
30. Severity and Priority in Software Testing
31. Defect Density
32. Cause and Effect Analysis
33. Cyber Security Basic Terms and Concepts
34. Introduction to Software Architecture
35. Memory Leak explained
36. Race Condition in Software
37. Off-by-one Errors

Hope that you find these software testing tutorials useful :)

Next, learn from the free Test Automation Tutorials.

What is Traceability Matrix?

In software testing, an important document is called Traceability Matrix (TM) or Requirements Traceability Matrix (RTM). This is the document that connects the requirements to the test cases. The connection or mapping of the requirements to test cases is many-many. This means that one requirement is tested by one or more test cases. Conversely, it is possible to have one test case addressing one or more requirements.

If you don't understand the RTM, view the video, Requirements Traceability Matrix that explains the RTM with an example.
Next, let us see some useful points about the Requirement Traceability Matrix.

1. A well-designed TM has the Req Ids and Test Case Ids. However, it should not have any text from the requirements or test cases because it is just a mapping. The TM could also contain module/ component/ sub-system Ids against each Req Id (see point no. 9).


2. A TM can be as simple as Req Ids on one axis and Test Case Ids on the other axis. For example, a TM implemented in MS Excel could have Req Ids in a single column (vertically) and Test Case Ids in multiple columns (horizontally). A symbol could mark which requirement maps to which test case.


3. The TM should be created as early as possible in the project. It becomes tedious to create if there are already numerous requirements and test cases.


4. The TM should be updated for every requirement change. New requirement is added or an existing requirement is changed or an existing requirement is deleted.


5. The TM should be updated when a new test case is written. This update could be the final step of completing the test case. If an existing test case is updated or enhanced, the TM should be reviewed for accuracy. The TM should be updated if any test case is retired.


6. One should be careful with workflow changes because they can impact multiple requirements and therefore multiple test cases.


7. It is simpler to update the TM if the requirements and test cases are modular and contain no repetitions.


8. TM is only a document which can become corrupted. Especially if multiple people write to it in an uncontrolled way. Therefore, the TM should be stored in a revision control system with locking and backup/ restore features.


9. If the TM contains module/ component/ sub-system Ids, it becomes simpler to identify the impacted modules whenever a requirement changes.


10. Some project management software or test management software provide automatic generation of TM based on requirements and test cases stored in the system. It is even possible to run the queries against the TM because all its information lives in a database.

Happy testing!