How to write the environment while reporting a bug in various bug tracking systems
-
How to write the environment while reporting a bug in various bug tracking systems
How to write the environment while reporting a bug in various bug tracking systems (Jira, Mantis, Pivotal, Trello, Bugzilla)
-
How is the process of the «Software Testing: Basics and Practice» course proceeded?
This article describes the main points that you will encounter when studying with us in online courses. Remember, you can always ask us any questions regarding the learning process.
-
Testing schemes from students of the course v.2
In the third home task on the «Software Testing: Basics and Practice» course, you are offered to complete the additional task which is to test any object of your choice, using different types of testing. We have already shown you such examples in the previous article but there are never too many examples. Applying different types of testing is the best chance to understand each of the testing types. In this article, we will present you some additional object testing schemes from our students.
-
Testing schemes from students of the course
On the «Software Testing: Basics and Practice» course our students have a chance to do the additional task – to test any object applying different types of testing. By applying different types of testing on the object, it is easier to understand the essence of each type of testing. Besides, it is actually funny. In this article, we will prove to you that it can actually be very funny through the examples of our students.
-
Working with checklists
Checklist – is a list which contains a number of necessary checks during testing of the software product. By checking the items on the list, a team or one tester can learn about the current state of the work performed and about the quality of the product.
-
How to describe similar bugs or the same bug in different browsers
Sometimes there are situations when the same bug is encountered on different pages or the same type of bug is shown in different places in the application or on the site . If you’ll describe similar issues as separated bug reports you can take up a lot of extra space in the bug tracker, confuse yourself and the developers, or spoil all the statistics of the defects.
-
How to write steps to reproduce the bug
Steps to reproduce is a piece of information that is needed to reproduce the bug. Steps to reproduce is a very important piece of information in the bug report. After finding the defect in the software, one must write the precise steps to reproduce the bug. It is important for steps to be stable. Take a very attentive look at the situation: what type of data was inputted? in what exact order? In such cases a video recording helps a lot.
-
How to write a proper bug report
Each company has its own rules for defect creation in the bug tracker – it depends on the company policy, development technology, bug tracker, project type and much more. But in any case, a good bug report has certain characteristics.
-
How is the process of the «Fundamentals of software testing» course proceeded?
This article describes the main points that you will encounter when studying with us in online courses. Remember, you can always ask us any questions regarding the learning process.
-
How to describe results in the bug report?
Defect (bug) is a discrepancy between the actual result of the program and the expected result. Defects are discovered during the software testing stage when the QA engineer compares the results of the program (component or design) with the expected result described in the requirements specification.
