How to write bug report like a pro in Jira. UI and API
courses.codemify.com/qa-pract... - Waitlist is over. Join our 50$ and 150$ memberships for people who can’t afford full-scale QA Bootcamp with mentors, webinars, and intense internships in US-based startups.
Thanks for watching! Here are timestamps if you want to move around :)
Timestamps
1:19 - Create Jira bug report for User Interface bug
3:35 - Create a perfect title for UI bug report
5:08 - What to include in the bug report description
5:10 - Pre-requisites
6:44 - Environment
7:46 - Steps to reproduce
8:59 - Expected result
9:16 - Actual result
9:46 - Assignee
10:33 - Current Sprint or Sprint Backlog
11:14 - Bug Priority
11:53 - QA Assignee
13:06 - Bug report attachment
14:51 - Practical US startup experience program with Codemify
15:36 - How to create an API bug report in Jira
25:02 - QA Engineer practical experience, more details
----------
Quick links to get in touch:
1. Software Quality Assurance Course - sign up for a free lesson here - codemify.com/course
2. Learn more info about Manual Testing and Automation Testing - codemify.com/blog
KZread playlists for you:
✅ More about QA Job: • About QA Job
✅ Our student's reviews: • Student Reviews
▶️JavaScript: • JavaScript
▶️WDIO: • WDIO
▶️API TEST Automation:
• API Test Automation
▶️Jira: • Jira
Change your carrier and become an IT professional with us.
❗️Info about our courses and mentorship - codemify.com/
✔️ Our QA courses: Manual and Automation Testing can be found here - codemify.com/courses
✔️ Registration form for the course - codemify.com/contact
✔️Our students: codemify.com/testimonials
✔️FAQ of QA automation: codemify.com/faq
✔️Follow us on Instagram :
/ codemify_
✔️ Get a free consultation or sign up for a course, questions about the course -
email - support@codemify.com
✔️ Telegram: t.me/codemifyschool
Пікірлер: 47
Thank you for this video ❤
@Codemify
Жыл бұрын
My greatest pleasure 🙌
спасибо за инфу, бро!
@Codemify
2 ай бұрын
My greatest pleasure!
Wel come bro 😊😊😊
Excellent video. Thanks for creating a real bug-finding lesson based on a well-known company's real product.🙂✨ In response to the level of priority this Instagram bug has and taking into consideration the huge amount of critical bugs in production present in Google / Google-mobile / Ebay etc. well-known products this bug/defect should be treated as the lowest priority. If Google bugs prevent the whole functionality presenting for months (in mobile for example) and eBay production bugs Prevent (for example) Part of their shop's shipment functionality are also corrected by Ebay in about a month... So it meant high-priority bugs for them 100% disabled sites, but they consider all the errors that block some of the most important functionality in production as a medium if not as the lowest priority.🙂 So the bug in the video only disappointed Instagram creators (clients), but prevent no functionality at all P.S. I also found a bug in this video. At 9:18 Expected and Actual result explanations should be swapped. Please check it. And thanks for the detailed and really helpful video.
@Codemify
Жыл бұрын
Thank you for such an open and detailed response!
Thank you! Great video! I don’t see the link for the waiting list…
@Codemify
Жыл бұрын
It's a first link in the description of the video
Hey, I think that you did a mistake for Expected and Actual result, because in Expected result we expect that everything is correct, but in actual result you have to write the actual behavior on the web , so Expected result has to be : Amount of followers are visible Actual result has to be: Amount of followers are invisible
@Codemify
9 ай бұрын
Great catch 🙌🏼 See first comment under this video :)
I wonder how long it's gonna take people to see that we have written actual result instead of expected 😁
@Avricha32
Жыл бұрын
Was just going to make a comment on that 😂
@annakuchumova9007
Жыл бұрын
Cough that 😅in the first but report actual vs expected are misplaced
@Codemify
Жыл бұрын
@@Avricha32 hahaha
@Codemify
Жыл бұрын
@@annakuchumova9007 haha great job! The future is bright 😁
@user-cx2qs6zb4b
Жыл бұрын
Great joke =) I had even written a comment but deleted it. 😁
Hi Sergio, wanted to ask you is there a mentor that will guide you throughout the program....How does your system work? As far as coaching/ menotes go? How long is the qa/ automation program combined? Thank you so much in advance......
@Codemify
Жыл бұрын
Good question! The total is 5 months. We do have multiple mentors who will assist you throughout the course with all of the questions and the startup work you gonna do.
@tiffanydrake1652
Жыл бұрын
Thank you so much for getting back with me Sergio, I really appreciate it. For automation do you also focus on teaching you SQL, and selenium?
@Codemify
Жыл бұрын
@@tiffanydrake1652 Yes, we do teach SQL and we teach Cypress for test automation as it's becoming the most popular test framework in the world 💪
I dont have priority field on my Jira account. Perhaps, it will be only in full paid version?
@Codemify
10 ай бұрын
Great Q! Priority is a configurable field. It is not required. In your case, the product owner is going through all the bugs and choosing them. So no worries about priority. But you can include it in the ticket description for practice for now
Hi man! According to your experience, how do you try keep yourself motivated with such monotonic job? I've passed an interview in a local IT company and being a manual QC engineer is extremely boring, I barely force myself to go to work...
@Codemify
Жыл бұрын
Great question! I'll give you two answers: 1. There are two types of people. Those who do their job as slowly as possible. And those do their job as quickly as possible and take more tasks and improve existing processes to make the company more profitable and to get a raise. 2. Not every QA(QC might be different) job is boring. It depends on your company, project, team, and most of your manager. I could do my job in 3 hours and I would spend the rest of my day learning coding, test automation, pretty much to get new skills. Half a year after I got an offer and moved to a QA Automation role with a $25k higher salary. So I would say it's not about the job, but about how you react at that job and what are you looking for in it 🙂
@Codemify
Жыл бұрын
Btw, you can always find a more exciding jobs and a team. AKA better fit
@Neo_Ne
Жыл бұрын
@@Codemify thanks for the advice. I'm thinking about switching to AQA or PM. Maybe it would be more exciting than doing monkey testing :)
@Neo_Ne
Жыл бұрын
@@Codemify Right the first time. It depends on the company and its attitude to the processes inside this company. For instance, having a particular quantity of bugs per one QA (QC) Engineer a day looks too odd, doesn't it?
@Codemify
Жыл бұрын
@@Neo_Ne You mean that in your company you are required to find certain amount of bugs per day?