How do you log bugs/defects?

In software testing, we use the bug report to log bugs. the bug report is a detailed document detailing the flaws discovered in the software application. The bug report comprises every detail regarding a bug, such as the description, the date the bug was discovered, the identity of the tester who discovered it, the name of the developer who corrected it. such as defect id, defect description, version, steps, status, priority.

bug report 是一份详细的文件，可以详细说明在软件应用中发现的缺陷。它包含了每一个关于bug 的细节，id , version， 描述，steps，发现的时间，谁发现的，谁修复的bug，修复的步骤，目前的状态。

                    Why do you need screenshots and logs to be attached to a defect/bug?

When the software quality assurance people and the software developers are members of two different teams, bug discovery and reporting could often be a source of conflict caused by misunderstanding.

Logs (log files) are the text files that record the activity and describe the performance of the service and the computer in general. During software testing, people use logs when the bug cannot be displayed on a screenshot or a video file. In most cases, it happens when there was an emergency shutdown. In this case, you need to write all the steps in the logs. Such attachments contain all the data needed to reproduce all the steps.

The screenshot is a digital photo of the display that is created with built-in functionality of OS or some other special program. It is better to attach screenshots using the formats like «.png», «.bmp», «.jpeg». They are generally available. the screenshot is the most popular attachment. Without a screenshot, it’ll be difficult to tell what and where the problem is. The screenshot allows you to compare and contrast the prior and current user interfaces.

我们使用系统自带的工具。最好使用的截图格式是png，bmp，jpeg. 他们都通常提供. 没有截图，很难讲清楚问题是什么或者说是在哪。截图可以帮助你能够对比出前后的情况。

Highlight the bug on the screenshot: place it in a rectangle or point it with a red arrow; When you work with a screenshot (add some frame or arrow), use the specifications of the built-in editor;

                                How would you prioritize your defect/bug?

I will ask myself three questions: 

• Does a bug affect one of the major flows in the product?
• 这个bug是否影响了产品的主要功能。
• What is the estimated number of users who will encounter this bug ? How important are these uses for me?
• 有多少user 会遇到这个问题，这些用户对我们来讲重要吗 ？
• How big will the effort to fix the bug be?
• 修复这个bug 需要多少努力？

              How do you go about writing test cases for a given requirement?

The basic objective of writing cases is to validate the test coverage of the application

Test case id, test data, steps to be executed, expected result, actual result, pass/fail

编写测试用例的基本目标就是验证应用程序的测试范围。对于每一个测试用例我们必须要有以下步骤。

          What is the difference between a use case and a test case?

A use case is used to define the systems that how to use the system for performing a specific task. and A Test case is defined as a group of test inputs, execution condition, and expected results which further lead to developing a particular test objective.

use case 描述的是客户跟系统和产品交互。而测试用例定义是一足测试的输入，执行条件，期待条件进一步导致了具体的测试目标。

             What is the difference between test scenario and test case?

Test Case is a set of actions executed to verify particular features or functionality , foucuse on how to test , while Test scenarios is more focused on what to test and verify the complete functionality of the software application.

The test scenarios are those derived from test case and give the one-line information about test.

the test cases are derived from test scenarios.

The test cases is low level documentation, and the test scenarios is high level documentation. 

The hirachey is requirements->test scenarios->test cases

A Test Case is a set of actions executed to verify a particular feature or functionality of your software application. A Test Case contains test steps, test data, precondition, postcondition developed for specific test scenario to verify any requirement..

测试用例是用来验证具体功能和特的一组行为。而测试scenarious 更偏重于测试什么，用来验证软件的完整性。