I’m the sole QA for a small online database company. I know API texting is lower on the pyramid than end to end testing but where do you start? Do you run tests to ensure to correct codes are being given on certain pages? Where would you begin if you were creating a test suite?
Hello guys,
I'm working on a REST API using Django Rest Framework and I'm adding all the available requests to Postman Collection so then I can just "publish" it so Frontend devs see what they can do with the API.
It looks like this:
https://preview.redd.it/hqni5h6ojmc81.png?width=262&format=png&auto=webp&s=741576324e413a3d02ab9ffbc8c2d6e04c99d7f3
Now I'm trying to figure out how to use Postman to test different sequences of requests:
For example test, I'd call TEST USER CREATION
- Auth.Login - Credentials - should return `access_token
- Auth.Check Logged In - should return 200
- User.create - should return 201
This is just one sequence from tons that I can think of but I don't know how to make Postman know when and which requests it should run.
From what I saw on the Internet, sometimes people use Collections as sequences of tests but aren't they just to organize the requests?
And even if I created a new Collection called TEST USER CREATION it would not automatically change the requests when I change them in the main Collection.
How could I do that?
I'm currently writing an AutoCAD plugin where I am having to wrap everything coming from the AutoCAD API in order to make it so that I could test using NUnit or whatever, as the tests can't run without AutoCAD running and the tests can't run while AutoCAD is running...
So is the only way around this to wrap everything or give up testing?
At my current fresh job as an Automation Engineer, I was hired to work with API testing using Postman (JavaScript). For me, the API testing area is quite new, though I know how the APIs are working, and I have worked previously with Javascript and Postman ( for some websites).
After one week of working, my manager proposed me a transfer to an entirely different team and project, to work with UI testing, using Cypress framework (also Javascript). He knows that I don't have experience with UI testing, especially Cypress, and he is willing to allocate time and resources for me to learn it.
So, I am kinda in a dilemma here, deciding between two big paths in the QA career. Both paths are new to me.
Please, help me decide which path should I take: API(Postman) or UI(Cypress/Jest) testing.
I have recently joined as a QA Automation tester in a team(I'm the only tester) and I have been told to build a Selenium framework from scratch using Python for testing activities which primarily involves UI and API Testing. I have previously worked on Cucumber BDD with Java in my last project. Pretty clueless with Python. Kindly suggest the best out of (ROBOT,PyTest,Behave). TIA
I recently joined a new company and since the day I have started I'm facing challenges in API testing. Client being client keep on pushing to get more done (both functional and automation) I'm getting the hang of functional but only able to do basic level of api automation so far. I'm really stressed because of this, and don't wanna continue. What should I do? Please suggest.
Resume below
Objective: I’m currently looking to add value by utilizing my skill set, knowledge, and expertise.
Tools & Technical Skills: Skilled QAE in performing Manual, Automated and mobile Testing in various SDLC methodologies. Fluently speak English, Russian and Bulgarian. I am business and technology oriented, analytical, diplomatic, communicative and respect different cultures. Work well in teams. Operating System/Languages - Windows, Apple/macOS, Android, iOS, LINUX, HTML, CSS, Java, SQL, PL/SQL. Mobile & Web Browser - IE, Firefox, Safari, Edge, Chrome, Opera Mini, Firefox Focus, Dolphin. Automated Testing Tools & IDE Selenium, Cucumber, Katalon Studio, IntelliJ. Defect & Test Management - Jira, Zoho, Zephyr. Databases, Languages, Tools - Oracle, Toad, SQL Developer, SQL, PL/SQL, MySQL, MongoDB, JSON Microsoft and other Tools - MS Office, MS Visio, MS SharePoint, Slack, WebEx, Skype, MS Teams, Snagit, FIleZilla, BrowserStack.
Education: Bachelor in Hospitality and Hotel Management - Albena University, Bulgaria.
IT and Quality Assurance Highlights:
- Well versed in testing processes and its implementation within Agile/Scrum methodologies.
- Experienced in Test Case and Test Scripts creation using best practice for Web and Mobile apps. throughout the phases of SDLC.
- Proficient in using various test and defect management tools – Jira, TestRail & Zephyr.
- Proficient in designing Test Plans, Test Cases and Scripts from User Stories and other artifacts.
- Expert in designing and developing detailed Automated Test Cases using Java for Web and Mobile AUT.
- Hands-on experience performing Backend Testing in MySQL, MS SQL, and Oracle using SQL.
- In depth experience and understanding of SDLC - Agile/Scrum, CI/CD, DevOps, Iterative and Waterfall.
- Good understanding of concepts and logics of programming languages - Java, HTML, CSS.
- Skilled in creating and maintaining Test Automation Framework using TestNG, Excel and Functions.
- Excellent ability to promptly recognize software project objectives to provide testing support.
- Very good in performing different types of tests – Manual and Automated, Unit, System Testing, User Acceptance Testing (UAT), Regression Testing, Ad-hoc Testing, E2E, API Testing.
- Proficient in Mobile Testing on Android, iPhone, iPad and Smart watches.
- Good understanding of testing mobile app using tools Katalon Studio, Perfecto Mobile and BrowserStack.
- Good understanding of wireless technologies -
Check out this informative article on https://www.impactqa.com/blog/api-testing-for-open-banking-operations/
I would like to ask if anyone here is experienced in this, I would like to ask for tips and tools, although I have open-sourced tools and paid ones by our company, this is just for a second opinion since this will be my first time to conduct for an API.
Thank you.
How do you seed the data for testing your APIs?
Currently, I'm using Playwright for UI testing, but I'd like to write API tests where I also plan to use Playwright. The tests will be ran against an actual DB and server, not mocked. I'd like to use them both as part of a CI/CD pipeline and also as a way for devs to test against their own development machines.
- Should each individual API test use a fixture to seed the database (also using the API), run the test, then remove the data (using the API)?
- Should you pre-seed all of the data before hand?
- Should each API route be tested individually or does it make more sense to have a test that combines adding data to the DB and then retrieving it?
Thanks!
EDIT: Thanks for the helpful responses everyone. It is really helpful to hear how other people are doing testing. I've decided to have each test be as self containing as possible. That is, it will create, read, and delete the data that it needs to perform the test.
Hi,
I am learning Full-stack developemnt from fullstackopen, I am on 4.8 Exercise.
I have discussed with my peers, looked at the solutions even took help of the faculty but was not about to solve this.
issue is
superagent object is not returning anything for however long timeout, it seems like application is paused.
here is code for the test
link to my github https://github.com/Suryapratap-R/FullStackOpen/tree/main/part4
As the title said, i had a nitrite reading of 0.5 ppm from tapwater. This contradicts my water provider's publication that states there should be <0.01ppm of nitrites in the water. I thought I had a bad test kit and picked up another one. Still 0.5ppm.
Im wondering if anyone has had the same experience or at least had some false positives on an API freshwater nitrite test?
I am toying with this idea of an API testing automated solution.
The problem I am trying to solve
Manual Testing: After a developer has written the APIs and given it to a test engineer, they test it using Insomnia or Postman. If no automation tests have been written, it involves rerunning tests every time there are changes to the API.
Automation Testing: If you have to get the API's test automated, you will pick a tool of your choice like JMeter or Karate and need a test engineer to write the test cases.
Setting up the CI/CD pipeline: After your team has created the tests, you need to configure this to run in Jenkins after every build or before the release.
Business users' inability to work with APIs: Since most of the tests are written by a test engineer, a business user has very little control over the data. They are not always comfortable working with complex JSON structures and managing test data.
Sharing of test results: Other than the PDF or excel sheet of the test data, there are not that many ways to share your APIs with your customer or business users.
Testing by business users: Your business user will have to recreate their own tests with their data sets to validate the API. They have to do everything that your team has done with their data sets.
What do you guys think of this idea? Is it worth to try? Makes any use case for tose who have been developing the APIs. I have not seen many solutions that offer this functionality
Do you even use Postman? If not, share what you use and how you get it done if possible? I have heard people talk about writing tests instead of using Postman, but I do not know how that works. I’d like to know what you guys do.
Hi everybody,
I have a question because i want to learn how to do a correct penetration test in mobile apps and APIs.
Someone know a good course or book that recommend me to start. My background is network and web pentest (SAST-DAST) but is other world.
regards!
I recently joined a new company and since the day I have started I'm facing challenges in API testing. Client being client keep on pushing to get more done (both functional and automation) I'm getting the hang of functional but only able to do basic level of api automation so far. I'm really stressed because of this, and don't wanna continue. What should I do? Please suggest. Background: 2YOE in selenium based automation testing, self taught API testing.
