Automation Framework for Event App

[Jahidul2543]

• [ ] Create a automation framework with 2 to 3 test cases. It must be same as this framework

Let me notify using this ticket when done ASAP.

[Jahidul2543]

@Jahidul2543 Task

• [ ] Give Jenkins Access
• [ ] Make jenksins job available for people to play arouund

[taneeza]

@Jahidul2543 bhai Salam, here is my repo link https://github.com/taneeza/B2301PicnicEvenetFramework I wrote 3 test cases, but for FormSubmission test, I couldn't write any assertion. I accepted the alert. but after that there was no change or message on the webpage that I could assert. Please have a look and let me know if I need to make corrections. Thank you.

[AyshaShetu]

https://github.com/AyshaShetu/PicnicEventB2301Framework. I tried 4 test cases. but also having same issue as Taneeza apu. this app does not give any message or notification for negative testing. manually when I put valid credential, it was giving me confirmation email but not through the testing . want to see how that works. having issue if I run tests from smoke test.

[Jahidul2543]

@taneeza and @AyshaShetu and others Can you create a bug report for the above issue? Do it separately? You can create an issue under this repo by cleaning New Issue and mark it as bug. Write detail bug report in the description. You can follow any format you know or find. Assign this task to @amran75

Few basic information must be there:-

When reporting a software bug, it is important to provide accurate and detailed information to help developers understand and reproduce the issue. Here are some essential components of a software bug report:

1. Title/Summary: A concise and descriptive title that summarizes the bug or issue.

2. Description: A detailed explanation of the bug, including the specific behavior or problem encountered, and the expected behavior. Be clear and specific, providing step-by-step instructions on how to reproduce the bug if possible.

3. Environment Details: Include information about the environment in which the bug occurred, such as the operating system, software version, hardware specifications, and any relevant configurations.

4. Steps to Reproduce: Provide a clear set of instructions that outline the exact steps required to reproduce the bug. This helps developers isolate and investigate the issue effectively.

5. Expected and Actual Results: Describe what you expected to happen and what actually occurred. Highlight any discrepancies or unexpected behavior that you observed.

6. Screenshots/Attachments: If applicable, include relevant screenshots, error messages, or any other visual aids that can help developers understand the issue better. Attach log files or any additional files that may be useful for debugging.

7. Impact and Severity: Indicate the impact of the bug on the software's functionality or the user's experience. Assess the severity level, such as critical, major, minor, or cosmetic, to help prioritize the issue.

8. Reproducibility: Specify whether the issue occurs consistently or intermittently. If intermittent, mention any patterns or conditions that may be related to the bug's occurrence.

9. Workaround: If you have discovered a temporary solution or workaround for the bug, provide details on how to mitigate the issue until it is resolved.

10. Additional Information: Include any other relevant information that can assist in understanding or resolving the bug, such as error logs, relevant code snippets, or related issues.

By including these components in your bug report, you can provide developers with the necessary details to understand, reproduce, and address the reported issue effectively.

[taneeza]

@AyshaShetu for valid registartion, it sent me confirmation email. I think the email address you used was not an actual email adress and that's why you didnt receive any email.

[taneeza]

@Jahidul2543 Jahid Bhai, I didn't find any bug. I was working on the bug report but I am very confused what bug to report. The only problem is I don't know how to write an assertion statement.

[Jahidul2543]

For example If you give an invalid email do you see any error message in the response? Or it says your request was sent successfully?

[taneeza]

got it, thanks

[taneeza]

Here is the Bug Report https://docs.google.com/document/d/1NzLghe05dsYnQ-qY7bs7FD3ZATRMkFHkUav2pB7UF88/edit?usp=sharing

P.S. Sorry sharing as a word doc for now. "You can create an issue under this repo by cleaning New Issue and mark it as bug" this part not done . I will do it later but ASAP.

[sarah-kh]

git repo for event app https://github.com/sarah-kh/EventAppFramework/tree/master

[AyshaShetu]

@taneeza apu I used valid credentials for valid registration test. if I use them manually, I was getting confirmation email. but through code it's not sending email. showing test is passed. as you are getting confirmation email I am thinking where I screwed up

[shejutiqa]

That is my git repo for picnic event : - https://github.com/shejutiqa/B2301PicnikeventFramework.git