Testim Beginner Tutorial 5 | Reporting and Integrations

Поделиться
HTML-код
  • Опубликовано: 14 июл 2024
  • What will we learn today:
    Reporting options overview
    How to filter and view results
    How to view Company Level Reports
    Check Run Results
    Reports email notification
    Integrations with other Platforms
    Slack Integration Demo
    Reporting options overview
    Step 1 - Login to your Testim Account
    Step 2 - Go to the Reports tab on the Insights section
    Step 3 - Can change the project and branch
    Step 4 - Select the time period
    Step 5 - Check the reports and activities
    Step 6 - Can switch to Team Productivity tab and check the analytics
    How to filter and view results
    Step 1 - Go to the Reports tab on the Insights section
    Step 2 - Click the Filter button
    Step 3 - Select the execution type and then select the desired checkboxes shown under that type
    Step 4 - Can also click on magnifying glass and enter your search criteria
    Step 5 - Click Apply and check the reports
    How to view Company Level Reports
    Step 1 - Click on your account profile image
    Step 2 - Click Reports
    Step 3 - Click on the Filter button
    Step 4 - In the Project section, select one or more projects
    Step 5 - Click Apply
    Step 6 - Check the reports
    Check Run Results
    Step 1 - Go to Runs section
    Step 2 - Can check results for executions, test runs, scheduled runs
    Step 3 - Can filter by timeline
    Reports Email Notification
    Step 1 - Go to Settings > Report
    Step 2 - Enter email and set weekly report notifications
    Integrations with external platforms
    Step 1 - Go to Settings > Integration
    Step 2 - Explore the different options and platforms
    For CI Integration Platforms
    Step 1 - Go to Settings --> CLI --> CI
    Step 2 - Select the CI platform from the dropdown list
    help.testim.io/docs/integrati...
    Slack Integration Demo
    Step 1 - Login to your Slack account
    Step 2 - On Testim, Go to Settings > Integration
    Step 3 - Select Bug Tracker > Slack > Add to Slack
    Step 4 - Select the Slack channel and allow to post notifications from Testim
    Step 5 - On Testim, create a scheduled run
    Step 6 - Select the Slack option in Notification
    Step 7 - Run and check
    All Free Tutorials 🟢 AutomationStepByStep.com/
    ▬▬▬▬▬▬▬
    Share with all who may need this
    If my work has helped you, consider helping any animal near you, in any way you can
    Never Stop Learning
    Raghav Pal
    ▬▬

Комментарии • 14

  • @mlkp6585
    @mlkp6585 4 дня назад

    Hi Raghav can you kindly suggest learning road map for Salesforce qa

    • @RaghavPal
      @RaghavPal  4 дня назад +1

      Sure, here's a suggested learning roadmap for Salesforce QA:
      Step 1: Foundational Knowledge (1-2 weeks)
      1. Salesforce Basics:
      * Understand the Salesforce platform, its features, and benefits.
      * Learn about the different types of Salesforce licenses (e.g., Essentials, Lightning, Enterprise).
      * Familiarize yourself with Salesforce terminology (e.g., objects, fields, records).
      2. Salesforce QA Fundamentals:
      * Learn about the role of a Salesforce QA in a project.
      * Understand the importance of testing in Salesforce implementations.
      * Familiarize yourself with common testing methodologies (e.g., Agile, Waterfall).
      Step 2: Salesforce Administration (2-4 weeks)
      1. Salesforce Administrator Certification:
      * Study for and obtain the Salesforce Administrator certification (ADM-201).
      * This will help you understand the administrative aspects of Salesforce.
      2. Salesforce Features and Functionality:
      * Learn about Salesforce features, such as:
      + Accounts, Contacts, and other standard objects.
      + Custom objects, fields, and relationships.
      + Page layouts, workflows, and approvals.
      + Reports, dashboards, and analytics.
      3. Salesforce Security and Access Control:
      * Understand how to manage user access and permissions.
      * Learn about security features, such as:
      + User roles and profiles.
      + Object-level security.
      + Field-level security.
      Step 3: Testing and Quality Assurance (4-6 weeks)
      1. Testing Fundamentals:
      * Learn about testing principles, methodologies, and frameworks.
      * Understand the different types of testing (e.g., unit testing, integration testing, user acceptance testing).
      2. Salesforce Testing Tools:
      * Familiarize yourself with Salesforce testing tools, such as:
      + Salesforce CLI.
      + Apex testing frameworks (e.g., ApexUnit, ApexMocks).
      + Selenium WebDriver.
      3. Test Automation:
      * Learn about test automation frameworks and tools, such as:
      + Selenium WebDriver.
      + Cypress.
      + TestNG.
      4. Defect Tracking and Management:
      * Understand how to track and manage defects using tools like JIRA or Trello.
      Step 4: Advanced Topics and Specializations (4-6 weeks)
      1. Apex Programming:
      * Learn the basics of Apex programming, including:
      + Apex syntax and data types.
      + Apex triggers and classes.
      + Apex testing and debugging.
      2. Lightning Component Development:
      * Familiarize yourself with Lightning component development, including:
      + Lightning component architecture.
      + Lightning component lifecycle.
      + Lightning component testing.
      3. Integration and API Testing:
      * Learn about integration testing and API testing, including:
      + REST and SOAP APIs.
      + API testing tools (e.g., Postman, SoapUI).
      4. Specialized Salesforce Modules:
      * Choose a specialized module to focus on, such as:
      + Salesforce Commerce Cloud.
      + Salesforce Marketing Cloud.
      + Salesforce Service Cloud.
      Step 5: Practice and Certification (2-4 weeks)
      1. Practice with Trailhead:
      * Complete Trailhead modules related to Salesforce QA and testing.
      * Practice building and testing Salesforce applications.
      2. Prepare for Salesforce QA Certification:
      * Study for and obtain the Salesforce QA certification (CRT-101).
      * Review and practice testing scenarios and case studies.
      Additional Tips
      * Join online communities, such as the Salesforce Trailblazer Community or Reddit's r/Salesforce, to connect with other Salesforce professionals and stay up-to-date on the latest developments.
      * Participate in online forums and discussion groups to practice your problem-solving skills and learn from others.
      * Consider finding a mentor or coach who can guide you through your learning journey.
      * Set aside dedicated time to practice and review the material regularly.
      Remember, this is just a suggested roadmap, and you should adjust it to fit your learning style, pace, and goals. Good luck..
      -

    • @mlkp6585
      @mlkp6585 3 дня назад

      @@RaghavPal Thank you so much for your guidance

  • @Multistar-456
    @Multistar-456 3 дня назад

    Sir i have doubt regarding selenium. Sir i am fresher learning selenium now. In companies for selenium existing code is available or we need to write sir. Sir please reply me sir please

    • @RaghavPal
      @RaghavPal  3 дня назад +1

      In most companies, there is a mix of both scenarios:
      a. Existing code: Many companies already have a established Selenium framework and test suites in place. In this case, as a new team member, you'll likely be working with existing code, which means you'll need to:
      * Understand the existing framework and its architecture.
      * Learn the coding standards and best practices followed by the team.
      * Update or modify existing tests to ensure they remain relevant and effective.
      * Add new tests to cover additional functionality or features.
      b. Writing new code: However, there may be situations where you need to create new code, such as:
      * When the company is adopting Selenium for the first time, and you're part of the team setting up the initial framework.
      * When new features or applications are developed, and you need to create tests from scratch.
      * When existing tests need to be refactored or rewritten to improve performance, maintainability, or reliability.

    • @Multistar-456
      @Multistar-456 3 дня назад

      @@RaghavPal thank you sir

  • @shivamraj100
    @shivamraj100 4 дня назад

    Hello sir, so after learning selenium and appium, i am looking for winium, but winium is not avaliable on youtube, i wanted to know, is it not that famous and if it is famous please make a course on it. i tried lot of channel but no one has made a dedicated playlist for winnium, and i m not able to learn a single thing from those videos

    • @RaghavPal
      @RaghavPal  3 дня назад

      There are a few possible reasons why Winium might not be as well-known as Selenium and Appium:
      * Winium is a relatively new tool, and its adoption rate might be slower.
      * It might be more niche or specialized, catering to a specific type of automation testing (e.g., Windows desktop applications).
      * The community around Winium might not be as large or active as those around Selenium and Appium.
      I will check if I can get enough time to create something on this.. For now you can check with its official page

    • @shivamraj100
      @shivamraj100 3 дня назад

      @@RaghavPal Can you suggest any tool to automate Desktop applications? If it’s possible. I mean I don’t even know if automating Desktop applications is possible at all by using java

    • @RaghavPal
      @RaghavPal  3 дня назад

      Yes, it is possible to automate desktop applications using Java. There are several approaches and tools that can be used to achieve this:
      1. Java Access Bridge (JAB): JAB is a Java-based API that allows Java applications to interact with native desktop applications on Windows platforms. It provides a way to automate interactions with desktop applications, but it has some limitations and is not widely supported
      2. Robot Class: Java's built-in `Robot` class can be used to simulate user interactions, such as mouse movements and keyboard input. However, this approach has limitations, as it relies on screen coordinates and may not work well with complex GUI applications
      3. UI Automation Tools: There are several third-party UI automation tools that provide Java APIs to interact with desktop applications. Some popular options include:
      * Sikuli: An open-source tool that uses image recognition to automate interactions with desktop applications.
      * AutoIt: A Windows-based automation tool that provides a Java API to interact with desktop applications.
      * TestComplete: A commercial tool that provides a Java API to automate interactions with desktop applications.
      * Robot Framework: An open-source test automation framework that provides a Java API to interact with desktop applications.
      Step 4: Evaluating Options
      When choosing a tool, consider the following factors:
      * Platform support: Does the tool support the target desktop platform (e.g., Windows, macOS, Linux)?
      * Ease of use: How easy is it to learn and use the tool?
      * Functionality: Does the tool provide the necessary features to automate the required interactions?
      * Cost: Is the tool free or commercial, and what are the associated costs?
      -

    • @shivamraj100
      @shivamraj100 3 дня назад +1

      @@RaghavPal Thank you for help sir, but i found easy way i used robot class and just pressed shutdown shortcut key and luckily that worked

    • @RaghavPal
      @RaghavPal  3 дня назад

      Great.. can continue with that