HTML-код
- Опубликовано: 23 окт 2024
- 🔥 All Free Tutorials - AutomationStep...
Gating Criteria refers to the check performed on the manual test plan to verify if it is feasible for automation
Checklist of Gating Criteria:
Scenario based approach is followed
Steps are atomic in nature (one step - one action)
Steps are in continuity
Expected result with every step
Functionality available in Framework (feasibility to add)
Dependency between Test Cases should be designed carefully
Prerequisite condition should be mentioned
Test Data should be available
Application stability, complexity, test environment, testing tools
▬▬▬▬▬▬▬
Every Like & Subscription gives me great motivation to keep working for you
You can support my mission for education by sharing this knowledge and helping as many people as you can
If my work has helped you, consider helping any animal near you, in any way you can
Never Stop Learning
Raghav Pal
▬▬▬▬ USEFUL LINKS ▬▬▬▬
Ask Raghav - bit.ly/2CoJGWf
Shorts Eng - bit.ly/3H9bifV
Shorts Hindi - bit.ly/3XY7XqN
GitHub Repositories - github.com/Rag...
Udemy - automationstep...
Stories - automationstep...
▬▬ CI | CD | DEVOPS ▬▬
Jenkins Beginner - bit.ly/2MIn8EC
Jenkins Tips & Trick - bit.ly/2LRt6xC
Docker - bit.ly/2MInnzx
Jenkinsfile - bit.ly/3JSMSZ7
Kubernetes - bit.ly/2MJIlMK
Vagrant - bit.ly/3MVKdBt
Ansible - bit.ly/3MUsY3h
▬▬ UI TESTING ▬▬
Selenium Beginners - bit.ly/2MGRS8K
Selenium Java Framework from Scratch - bit.ly/2N9xvR6
Selenium Python - bit.ly/2oyMp5x
Selenium 4 - bit.ly/3AiJOlP
Selenium Tips - bit.ly/2owxc50
Selenium Builder - bit.ly/2MKNtlq
Katalon Studio - bit.ly/2wARFdi
Robot Framework with RIDE- bit.ly/2Px6Ue9
Robot Framework with Eclipse - bit.ly/2N8DZxb
Protractor - bit.ly/2KtqVkU
AccelQ - bit.ly/3PlsAsh
Test Project - bit.ly/2DRNJYE
Cucumber BDD - bit.ly/3Cnno4z
Cypress - bit.ly/3PpEukM
Playwright - bit.ly/3iuPByJ
WebdriverIO - bit.ly/3IJyofA
XPath & Web Locators - bit.ly/3PpEvoQ
▬▬ API TESTING ▬▬
Web Services (API) - bit.ly/2MGafL7
SoapUI - bit.ly/2MGahmd
Postman - bit.ly/2wz8LrW
Postman 2022 - bit.ly/3JWm4qX
Rest Assured - bit.ly/3zUdhRD
Karate API Testing - bit.ly/3w3H5Ku
General - bit.ly/2PYdwmV
JMeter API Testing - bit.ly/3AgVPar
Katalon Studio API Testing - bit.ly/2BwuCTN
API Mocking - bit.ly/3bYPsjS
▬▬ MOBILE TESTING ▬▬
Appium - bit.ly/2ZHFSGX
Mobile Playlist - bit.ly/2PxpeUv
▬▬ PERFORMANCE TESTING ▬▬
JMeter Beginner - bit.ly/2oBbtIU
JMeter Intermediate - bit.ly/2oziNVB
JMeter Advanced - bit.ly/2Q22Y6a
JMeter Tips & Tricks - bit.ly/2NOfWD2
Gatling - bit.ly/3QrWfkV
Performance Testing - bit.ly/2wEXbLS
▬▬ SOURCE CODE MANAGEMENT ▬▬
Git & GitHub - bit.ly/2Q1pagY
GITLAB - bit.ly/2kQPGyQ
▬▬ IDE ▬▬
Eclipse - bit.ly/3AnRhQP
IntelliJ IDEA - bit.ly/3AnyDZ8
Visual Studio Code - bit.ly/2V15yvt
▬▬ PROGRAMMING ▬▬
Java Beginners - bit.ly/2PVUcXs
Java Tips & Tricks - bit.ly/2CdcDnJ
Groovy - bit.ly/2FvWV5C
JavaScript - bit.ly/2KJDZ8o
TypeScript - bit.ly/3dvJBmz
Python - bit.ly/2Z4iRye
Ruby - bit.ly/3JRRmzf
▬▬ BUILD TOOLS ▬▬
Maven - bit.ly/2NJdDRS
Gradle - bit.ly/30l3h1B
▬▬ CLOUD SERVICES ▬▬
Browserstack - bit.ly/3w7kxZn
Saucelabs - bit.ly/3w7kAo1
LambdaTest - bit.ly/3C6TBwM
▬▬ DATA FORMATS ▬▬
JSON - bit.ly/3w450tq
XML - bit.ly/3PqRneH
▬▬ OTHERS ▬▬
Virtualization on Windows - bit.ly/2SItIL9
Mock Interviews - bit.ly/3QGwwVJ
Redis - bit.ly/2N9jyCG
Misc - bit.ly/2Q2q5xQ
Tools & Tips - bit.ly/2oBfwoR
QnA Friday - bit.ly/2NgwGpw
Sunday Special - bit.ly/2wB23BO
-
Hi Raghav, a couple if years ago i was in charge of a project that was building new APIs for the company, i started learning postman and with some effort i create a suite of functional and integration tests that validate through different flows the behavior of the UI application.( i used dinamic variables that carry on the data from one endpoint to the other)This suite is used for backend regression often and i was able to discover a lot of bugs early in the dev cycle and release sooner. I also integrated those tests with devops( not to the point of being part of the ci\cd but close since i run them manually before deployment the code to the next environment, uat or prod) my question for you is this. I not considered my self an automation engineer( i don’t even know if i am using a framework ) so , even when this system works what i am missing? And how do you call what i am doing
Robert
What you are doing is *API testing*, and it is a very important part of software development. API testing ensures that the APIs that your company builds are working as expected and that they can be used correctly by the applications that consume them.
You are using a very effective approach to API testing by using Postman to create a suite of functional and integration tests. You are also using dynamic variables to carry data from one endpoint to the other, which allows you to test complex workflows.
The fact that your suite is used for backend regression often and that you have been able to discover a lot of bugs early in the dev cycle is a testament to the effectiveness of your approach.
You are also integrating your tests with DevOps by running them manually before deployment to the next environment. This is a good start, but there is room for improvement.
To fully integrate your tests with DevOps, you should automate the execution of your test suite and incorporate it into your CI/CD pipeline. This will allow you to run your tests automatically every time you deploy new code, which will help you to catch bugs early and release code more quickly and confidently.
You should also consider using a test automation framework. A test automation framework is a set of tools and libraries that can help you to write and execute your tests more efficiently. Some popular test automation frameworks for Postman include:
* Newman
* Karate
* TestCafe
* Katalon Studio
Using a test automation framework will help you to:
* Write more robust and maintainable tests
* Execute your tests in parallel
* Generate reports on the results of your tests
* Integrate your tests with CI/CD pipelines
Overall, you are doing a great job with API testing. You are using a very effective approach and you are seeing the benefits of your work. However, there is still room for improvement. By automating your tests and integrating them into your CI/CD pipeline, you can further improve the efficiency and effectiveness of your testing efforts.
*How to call what you are doing*
What you are doing is API testing, but you could also call it *test automation*, *automated testing*, or *regression testing*. It is up to you to decide which term you prefer.
Some people may say that you are not a true automation engineer because you are not using a test automation framework. However, I believe that anyone who is writing and executing automated tests can be considered an automation engineer.
The most important thing is that you are using your skills to improve the quality of the software that your company builds.
thank you@@RaghavPal for taking the time to answer me. It was a very usefull your explanation . I will be watching some of your courses and probably asking more questions. Have a very good day!
Hi Raghav,Thanks a bunch for all videos. I don't know how to express my thanks ,just god bless you more more. But I need to know if it will be possible that you explain us more in deep regarding REST API tuto , explain some concepts such as API versioning,JWT,cache control,SDK,OAuth,internal traffic,cache control . please awaiting for your reply. thanks
So nice of you, will plan on these topics
Thanks @@RaghavPal , so we will wait for that
Hello sir big fan of yours just started doing manual to automation learning can you tell me how I can add personal project work in cv bit confused about it how can I show 2 years experience to get the job
Kusum
Adding personal projects to your CV can significantly enhance your profile, especially when transitioning from manual to automation testing. Here's how you can showcase your personal projects and experience:
1. Create a 'Projects' Section: Add a dedicated section titled 'Key Projects' or 'Personal Projects' to your CV
2. Project Details: For each project, include the name, technologies used, your role, and the impact or results of the project. Keep it concise but informative.
3. Relevance: Ensure the projects are relevant to the job you're applying for. Highlight aspects of the project that align with the job description.
4. Quantify Your Experience: Where possible, use numbers to describe your success, such as 'reduced test execution time by 50%' or 'automated 30+ test cases'.
5. Use Action Verbs: Start bullet points with action verbs like 'developed', 'implemented', or 'automated' to describe your contributions
For the experience section, you can list any relevant work, including freelance or part-time roles, that involved automation or relevant skills. Describe your responsibilities and achievements, and if possible, quantify them to show the value you added to the project or organization.
Remember, the goal is to demonstrate that you have practical experience and skills in automation, even if it's not in a traditional employment setting.
Good luck with your learning and job searchx
Hi sir , I would like to know about the interview process for the tester role.
I attended an interview in which, I was able to clear the first two rounds which included analytical round -1(didn't ask for any 'test' definitions like regression, re-test, which was more related to their project) & coding round . In analytical round 2..the questions were more related to their project & didn't include any Testing-related questions.
If so, the companies will ask questions like these for the process, I would request you to help in clearing these rounds. And I do have an experience of 1.5 yrs
ThankYou!
Swetha
If you like can watch some of my Mock Interviews here - ruclips.net/p/PLhW3qG5bs-L-9kungiQkvTzZSykK-cEEC
Here are some of the questions that you may be asked in the interview process for the tester role:
* **Technical questions:** These questions will assess your knowledge of testing concepts and tools. Some examples of technical questions include:
* What is the difference between black-box testing and white-box testing?
* What is the difference between functional testing and non-functional testing?
* What is a test case?
* What is a test plan?
* What is a bug?
* What are the different types of bugs?
* How do you prioritize bugs?
* How do you track bugs?
* What is regression testing?
* What is re-testing?
* What is a test suite?
* What is a test environment?
* What are the different types of testing tools?
* **Behavioral questions:** These questions will assess your soft skills, such as communication, teamwork, and problem-solving skills. Some examples of behavioral questions include:
* Tell me about a time when you had to work with a difficult team member.
* How do you handle stress?
* How do you stay organized?
* How do you learn new things?
* What are your strengths and weaknesses as a tester?
* Why are you interested in this position?
* What do you know about our company?
* **Project-specific questions:** These questions will assess your knowledge of the specific project that the company is working on. Some examples of project-specific questions include:
* What are the different types of tests that you would run for this project?
* What are the challenges that you anticipate facing in testing this project?
* How would you track the progress of the testing?
* How would you communicate the results of the testing to the team?
If you have 1.5 years of experience as a tester, you should be able to answer most of these questions. However, it is still a good idea to practice answering these questions so that you can be prepared for the interview. You can find a list of common interview questions for testers online.
Here are some additional tips for clearing the interview process for the tester role:
* Do your research on the company and the project that you are interviewing for.
* Be prepared to answer technical questions.
* Be able to demonstrate your soft skills.
* Be confident and enthusiastic.
* Ask questions about the company and the project.
I hope this helps!
@@RaghavPal Thank you for giving me a hand on this !
How do i report bugs in azure dev ops what is the good practic . we are using selenuim with TestnG
Shaunak
Reporting bugs effectively in Azure DevOps is crucial for maintaining high-quality software. Here are some best practices for reporting bugs:
1. Use the Bug Work Item Type:
- In Azure DevOps, use the Bug work item type specifically designed for tracking code defects
- Bugs share standard features with other work item types (such as user stories and issues) but offer additional bug-specific capabilities.
2. Capture Detailed Information:
- When reporting a bug, provide as much detail as possible:
- Steps to Reproduce: Clearly describe how to reproduce the issue step-by-step.
- Expected Result: Explain what the expected behavior should be.
- Affected Browsers/Devices: Mention the browsers or devices where the bug occurs.
- Branches Affected: Specify which branches are impacted.
- Screenshots: Attach relevant screenshots to illustrate the issue.
- Any other relevant context.
3. Templates and Automation:
- Use templates to enforce consistent bug reporting practices⁶.
- Consider automating bug creation using tools like Selenium and TestNG. For example, capture screenshots automatically when a test fails and include them in the bug report.
4. Integration with Test Tools:
- Azure DevOps integrates with various test tools.
- Capture bugs directly from your test runs, linking them to specific builds, releases, and tests
5. Project-Specific Details:
- When creating a bug, fill in essential details:
- Assigned To: Assign the bug to the appropriate team member.
- Title: Provide a concise yet descriptive title.
- Iteration Path: Specify the iteration or sprint where the bug was found.
- Area Path: Indicate the relevant area of the application.
Remember that effective bug reporting helps the development team address issues promptly.
By following these practices, you'll contribute to better software quality
Hi sir can you help to read from Excel file and same data is there in pg database and then excel and pg database data should compare if any rows are not matching it should display those not matching records from Excel and pg database by using playwright js
Sanjeev
I will need more details and context on this, what exactly you are using, what have you tried etc
@@RaghavPal Hi sir developer inserted Excel data into postgre database and as tester I need to check all the rows inserted correctly or not into the postgres data base count should match and all the rows data should match by using playwright JavaScript..I can able to read data from pg database and Excel but unable to compare both data is matching or not sir
Here are the steps involved in comparing the data from an Excel file and a PostgreSQL database using Playwright JavaScript:
1. Import the necessary libraries, including playwright, xlsx, and psycopg2.
2. Open the Excel file using the xlsx library.
3. Read the data from the Excel file into a list of dictionaries.
4. Connect to the PostgreSQL database using the psycopg2 library.
5. Query the database for the data in the same table as the Excel file.
6. Create a list of the records from the database.
7. Compare the lists of records.
8. If the lists are not the same, print an error message.
Here is an example of how to do this in JavaScript:
```javascript
const playwright = require('playwright');
const xlsx = require('xlsx');
const psycopg2 = require('psycopg2');
async function main() {
// Open the Excel file.
const workbook = await xlsx.readFile('data.xlsx');
// Read the data from the Excel file into a list of dictionaries.
const data = workbook.Sheets[0].Rows.map(row => ({
name: row[0],
email: row[1],
}));
// Connect to the PostgreSQL database.
const connection = await psycopg2.connect({
host: 'localhost',
port: 5432,
database: 'my_database',
user: 'my_user',
password: 'my_password',
});
// Query the database for the data in the same table as the Excel file.
const rows = await connection.query('SELECT * FROM users');
// Create a list of the records from the database.
const databaseRecords = rows.map(row => ({
name: row[0],
email: row[1],
}));
// Compare the lists of records.
if (data !== databaseRecords) {
console.log('The data in the Excel file and the PostgreSQL database do not match');
}
}
main();
```
This code will read the data from the Excel file, connect to the PostgreSQL database, and compare the data from the two sources. If the data does not match, an error message will be printed to the console.
I hope this helps
@@RaghavPal Thanks alot sir for your response..I have learnt playwright by watching your videos.. I want to learn more about excel reading and api testing do we have any course for the same sir
Can check here Sanjeev - automationstepbystep.com/
how do i report the bug in azure devops . we are using selenuim web driver with testNG
Shaunak
Reporting bugs effectively in Azure DevOps is crucial for maintaining high-quality software. Here are some best practices for reporting bugs:
1. Use the Bug Work Item Type:
- In Azure DevOps, use the Bug work item type specifically designed for tracking code defects
- Bugs share standard features with other work item types (such as user stories and issues) but offer additional bug-specific capabilities.
2. Capture Detailed Information:
- When reporting a bug, provide as much detail as possible:
- Steps to Reproduce: Clearly describe how to reproduce the issue step-by-step.
- Expected Result: Explain what the expected behavior should be.
- Affected Browsers/Devices: Mention the browsers or devices where the bug occurs.
- Branches Affected: Specify which branches are impacted.
- Screenshots: Attach relevant screenshots to illustrate the issue.
- Any other relevant context.
3. Templates and Automation:
- Use templates to enforce consistent bug reporting practices⁶.
- Consider automating bug creation using tools like Selenium and TestNG. For example, capture screenshots automatically when a test fails and include them in the bug report.
4. Integration with Test Tools:
- Azure DevOps integrates with various test tools.
- Capture bugs directly from your test runs, linking them to specific builds, releases, and tests
5. Project-Specific Details:
- When creating a bug, fill in essential details:
- Assigned To: Assign the bug to the appropriate team member.
- Title: Provide a concise yet descriptive title.
- Iteration Path: Specify the iteration or sprint where the bug was found.
- Area Path: Indicate the relevant area of the application.
Remember that effective bug reporting helps the development team address issues promptly.
By following these practices, you'll contribute to better software quality
Yes
ok
7:00 Start watching this video from here to save some time
thanks for adding
Hi
Hi M D
Hi Raghav, could you please help me on the cypress cucumber framework in the following maner?
Feature: Orange CRM
Scenario Outline: TC REG Validate Orange CRM application
Given I login with data (, )... Preconditions:LoginAOrangeCRMpplication
Then validate that the Orange CRM Dashboard page with data (menuItems)...DashBoard:verifyMenuItems
Examples:
| UserID | Password |
| Admin | admin123 |
in above Preconditions is class file LoginAOrangeCRMpplication is function in that class
Lokesh
The code you have provided is a Cucumber feature file. It defines a feature called "Orange CRM" and a scenario called "TC REG Validate Orange CRM application". The scenario has two steps:
1. The first step is to login to the Orange CRM application with the specified user ID and password. This step uses the `Preconditions` keyword, which is a placeholder for a function that will be defined in a separate class file.
2. The second step is to validate that the Orange CRM Dashboard page is displayed. This step uses the `DashBoard` keyword, which is another placeholder for a function that will be defined in a separate class file.
The `Examples` section defines a list of data that will be used to run the scenario. In this case, there is only one row of data, which specifies the user ID and password to use when logging in.
To implement this code, you will need to create two class files: one for the `Preconditions` function and one for the `DashBoard` function. The `Preconditions` function should contain the code to login to the Orange CRM application. The `DashBoard` function should contain the code to validate that the Orange CRM Dashboard page is displayed.
Once you have created these two class files, you can run the Cucumber feature file by using the Cypress command line tool.
Here are some additional resources that you may find helpful:
* Cypress documentation: docs.cypress.io/
* Cucumber documentation: cucumber.io/docs/
I hope this helps