usmanf07
commented
10 months ago Screenshots could have been helpful. Improper bug reporting format
Closed AliAhsan69 closed 10 months ago
usmanf07
commented
10 months ago Screenshots could have been helpful. Improper bug reporting format
AliAhsan69
commented
10 months ago Thanks for the feedback I just want confirm, is it improper format due to only the screenshot or the rest format is wrong aswell?
On Tue, 28 Nov 2023, 01:00 Usman Faisal, @.***> wrote:
Screenshots could have been helpful. Improper bug reporting format
— Reply to this email directly, view it on GitHub https://github.com/RohmaAr/SQE/issues/1#issuecomment-1828504850, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYNAQDJ3XWG65OM5ZS5STQDYGTWM3AVCNFSM6AAAAAA7Q626J6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRYGUYDIOBVGA . You are receiving this because you modified the open/close state.Message ID: @.***>
usmanf07
commented
10 months ago Screenshots are a must in reporting bugs. Moreover, in the above report, only the steps part is valid. Formally, the following are required in bug reporting format:
Also you can provide any other information that might be relevant or helpful in resolving the bug
AliAhsan69
commented
10 months ago Once again thanks for the feedback, can you please review the document for the deliverable 2 that I have uploaded on the classroom. In that there are more detailed analysis of each issue, gap analysis aswell, as well as more detailed exection steps
On Tue, 28 Nov 2023, 01:17 Usman Faisal, @.***> wrote:
Screenshots are a must in reporting bugs. Moreover, in the above report, only the steps part is valid. Formally, the following are required in bug reporting format:
- Title: Provide a concise yet descriptive title for the bug report.
- Environment: Detail the environment in which the bug occurred. Example system/windows version, the device being used
- Steps to Reproduce
- Expected/Actual Behavior
- Screenshots/Logs/Errors in Console/Exceptions/Error Codes
- If there is any Additional Information, mention it very briefly and to the point under the heading of "Additional Information"
Also you can provide any other information that might be relevant or helpful in resolving the bug
— Reply to this email directly, view it on GitHub https://github.com/RohmaAr/SQE/issues/1#issuecomment-1828520425, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYNAQDKJY4X3FTO42C7FI63YGTYOFAVCNFSM6AAAAAA7Q626J6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRYGUZDANBSGU . You are receiving this because you modified the open/close state.Message ID: @.***>
usmanf07
commented
10 months ago Test Case Design & Bug Reporting are two different things. Even test case execution is not similar to bug reporting. You have been given marks for the document. The bug reporting had separate marks. In your deliverable you are required to report issues/bugs on github, not in document. Same will be followed if you will be working in a company in future.
Test Cases are Designed in Documents Issues are reported on github
AliAhsan69
commented
10 months ago Registration issue has been removed successfully.
Before issue:
1.Go to http://localhost:8080/register
2.Enter your info
3.Click register
4.Generates a whitelabel error
Afrer solving:
1.Go to http://localhost:8080/register
2.Enter your info
3.Click register
4.Generates the login page where you can enter the new credentials and login to the website
The application does not allow new user to register when cliked on "Register here" on the Login Page Steps To generate the Isuue:
if you run the code for the 1st time, this error will generate, of you do this the second time same error will come, but on the third try the user is being successfully registered. As there have already been two saved users in the database and their ids are 1 and 2 respectively whe the code is executed for the 1st time and you regester 1st user the program generates the next id as 1 which causes the error for the first two users registration