keep💖

@softwaretesting2023

2 ай бұрын

Thank you

Hello mam, Please make a video about jira tool and how a tester use it - as for project management tool and for bug tracking tool and bug reporting tool. Regards

@softwaretesting2023

2 ай бұрын

Sure, Thank you for reaching out. You can check some of my videos i.e. about Jira Tool, that i have signed up to document my test cases. Also, I have installed Zephyr scale in order to design my test cases. Please go through those videos, and if you have any specific questions, feel free to ask. Jira, developed by Atlassian, is a powerful platform used by software development teams. It seamlessly combines project management, issue tracking, and collaboration features. For now answering your question in short, to give you some idea about Jira. Jira in a Nutshell: Your All-in-One Tool What Is Jira?: Jira is a versatile platform for project management and bug tracking. Tester’s Role: Bug Reporting: Log bugs with clear details (steps, expected vs. actual results). Workflow Management: Customize workflows and track bug status. Test Case Management: Create and link test cases. Collaboration: Discuss issues, share files, and collaborate. Best Practices: Use descriptive titles, labels, and components. Remember: Jira is your command center-where bugs are tracked, projects unfold, and teamwork thrives! Explore more about Jira Software.

Respected madam, can You help me to know how to test an application without knowing its requirements and also write test cases and prepare report of that as a beginner? Thank you.

@softwaretesting2023

3 ай бұрын

Hi, testing an application without documented requirements can be challenging, but it’s not impossible. As a beginner, here are some practical approaches you can take: by emphasizing user experience, exploratory testing, and risk-based approaches.” Explaining some tips in detail for you to follow. Hope this helps. A) Collect whatever Documentation you have- Method 1: Start by gathering whatever little documentation you can find. It could be a basic backlog (in agile projects), a help file, an email, an older version of the Business Requirements Document (BRD) or Functional Requirements Document (FRD), or even old test cases (check your Application Lifecycle Management tools). Investigate and ask around - there's often some documented information, even if it's minimal. Method 2: Use the older or current version of the application as a reference. Explore how the existing functionality works and use it to guide your testing for future releases. Sometimes, the best way to understand an application is by interacting with it directly. Method 3: Engage with project team members. Discuss the application with developers, business analysts, and other stakeholders. They might provide insights or context that isn't explicitly documented. B) Leverage Your User Experience: As a software user yourself, rely on your experience. For example, if you're testing a mobile banking app, think about common scenarios you encounter as an online banking customer. How would you transfer funds? What steps do you follow? Apply this knowledge to your testing. C) Exploratory Testing: Explore the application without predefined test cases. Click around, interact with different features, and observe how the app behaves. Note any unexpected behavior, inconsistencies, or issues. Keep detailed notes during exploratory testing. Document what you did, what you observed, and any potential defects. D) Risk-Based Testing: Identify critical areas of the application. Focus your testing efforts on these high-risk features or functionalities. Prioritize your testing based on potential impact and likelihood of failure. This approach helps you allocate your limited testing time effectively. E) Mind the Basics: Even without formal requirements, remember the fundamental principles of testing: Functional Testing: Verify that the application performs its intended functions correctly. Usability Testing: Evaluate the user interface, navigation, and overall user experience. F) Security Testing: Check for vulnerabilities and ensure data protection. G) Performance Testing: Assess responsiveness, load handling, and scalability. H) Compatibility Testing: Test across different devices, browsers, and operating systems. I) Document Your Findings: Prepare a test report summarizing your observations, defects, and any risks you've identified. Include screenshots, steps to reproduce issues, and severity levels. Be clear about what you tested, what you couldn't test due to lack of requirements, and any assumptions you made. Remember, while testing without requirements is challenging, your critical thinking, creativity, and attention to detail will be your allies. Good luck with your Testing Journey. Feel free to ask if you have any other queries.

@softwaretesting2023

3 ай бұрын

You may also go through my other videos I posted previously related to Writing Test cases step-by-step. I am sure it will help you.

@sankalanbiswasofficial

3 ай бұрын

Yes madam I am watch your videos & its very helpful for me. Thank you.@@softwaretesting2023