Don't all types of testing prevent regression? Why is it a category? It would be good if you give an example of a regression test that doesn't fall into other types of testing mentioned.
Not neccessarily, you have a test suite of existing regressions to ensure the existing functionalities are not broken by new code, which can happen quite a bit. For example, functional testing is only concerned with the new functionality introduced, not necessarily whether other existing functionalities are impacted. Usually it is automated by writing all the test cases onto a repo and running it every time new code is introduced or on a daily period as I have seen at my workplace.
Good piece as usual. Something that prevents these tests occurring is the cost involved. Especially for apis/programs that are part of a large application. Often stubs are used but invariably they don't and can't reflect real world interaction. I'd also like to add a wrinkle. What about testing when it involves fixing a sev1, I.e. severe service impacting, problem?
The problem is we the developers like to include tests, but the management like to have more development over testing, and doesn't allow budget for unit testing, nor testing team. So, it's not our fault if the company we work for is cheap.
Why does the most basic testing (unit test) is not on the list ? I know, it's a bit different (because testing the underlying method instead of calling the endpoind), but still, it should be the first and most important tests when writing APIs. EDIT: Ok ok, the presented list is not the for the API *devellopers*, but more for a sort of QA team that would have access to the endpoints only.
It seems he completely omitted the tests that devs make(unit, integration, even end-to-end) within the project and only mentioned the ones QA perform. It's not just unit tests anymore. With containers you can easily add external dependencies to your test suite, apply your schema to a DB via something like liquibase and test interaction with a real DB/Kafka/other stuff on every test run. And because microservices are relatively small it is extremely convenient.
Because this is not a list about all tests in general. This is focused on API testing which involves calling an endpoint. I don’t see any value talking about unit tests, there are multiple videos about it. The target audience of this video is not complete beginners in testing.
@Steelrat1994 That makes a lot of sense ! Thank you for your answer . (I've also thought about those other tests you've mentioned, but i was less surprised as they could be assimilated to the ones presented; for exemple: a functional test, if automated, could be considered as an e2e test... ). The key in my mistake was about forgetting the QA team 😅 --> for the last 15 years, I've used most of those tests (with containers, liquibase, ... very useful stuff indeed), but i was often Dev *and* QA ... that's why I couldn't consider testing my API's with those mentioned tests only. Now I understand 🙇♂️
Hi, nice videos. Some topic for future what I'm currently looking for is SQL databases synchronisation, but on premis not cloud. Limits, pros, cons, general requirements. Looking forward for such a video.
My tests have mostly been written in Python, and generally speaking, automated testing happens in the language you feel comfortable writings the test cases in. However tools like SOAPui(which also does REST), jmeter, rest-assured or K6 provide additional functionality.
Don't all types of testing prevent regression? Why is it a category? It would be good if you give an example of a regression test that doesn't fall into other types of testing mentioned.
Not neccessarily, you have a test suite of existing regressions to ensure the existing functionalities are not broken by new code, which can happen quite a bit. For example, functional testing is only concerned with the new functionality introduced, not necessarily whether other existing functionalities are impacted. Usually it is automated by writing all the test cases onto a repo and running it every time new code is introduced or on a daily period as I have seen at my workplace.
Good piece as usual. Something that prevents these tests occurring is the cost involved. Especially for apis/programs that are part of a large application. Often stubs are used but invariably they don't and can't reflect real world interaction.
I'd also like to add a wrinkle. What about testing when it involves fixing a sev1, I.e. severe service impacting, problem?
What software is used to create this beautiful presentation?
Animation tools: Adobe Illustrator and After Effects.
very vague
looks like fuzz testing is part of security, ui and smoke are part of integration
Thank you for sharing this video..... any solution recommendations for each of the 9 Testing Types??
Great channel and great content.
hello, can you also cover contract testing?
Nice video Alex and team. Just to add one thing, UI and UX are different types of testing. what you explained is UX testing, not UI. THankyou :)
The problem is we the developers like to include tests, but the management like to have more development over testing, and doesn't allow budget for unit testing, nor testing team. So, it's not our fault if the company we work for is cheap.
Man, you are the best
Great thanks
Why does the most basic testing (unit test) is not on the list ? I know, it's a bit different (because testing the underlying method instead of calling the endpoind), but still, it should be the first and most important tests when writing APIs.
EDIT: Ok ok, the presented list is not the for the API *devellopers*, but more for a sort of QA team that would have access to the endpoints only.
It seems he completely omitted the tests that devs make(unit, integration, even end-to-end) within the project and only mentioned the ones QA perform.
It's not just unit tests anymore. With containers you can easily add external dependencies to your test suite, apply your schema to a DB via something like liquibase and test interaction with a real DB/Kafka/other stuff on every test run. And because microservices are relatively small it is extremely convenient.
Because this is not a list about all tests in general. This is focused on API testing which involves calling an endpoint. I don’t see any value talking about unit tests, there are multiple videos about it. The target audience of this video is not complete beginners in testing.
@Steelrat1994 That makes a lot of sense ! Thank you for your answer .
(I've also thought about those other tests you've mentioned, but i was less surprised as they could be assimilated to the ones presented; for exemple: a functional test, if automated, could be considered as an e2e test... ).
The key in my mistake was about forgetting the QA team 😅 --> for the last 15 years, I've used most of those tests (with containers, liquibase, ... very useful stuff indeed), but i was often Dev *and* QA ... that's why I couldn't consider testing my API's with those mentioned tests only. Now I understand 🙇♂️
As you mentioned ut is nit api testing
Hi, nice videos. Some topic for future what I'm currently looking for is SQL databases synchronisation, but on premis not cloud. Limits, pros, cons, general requirements. Looking forward for such a video.
where you are taking icons for your presentation?
thank you!
Can someone mention tools are used for Api testing rather than Postman especially for integration testing and load testing
My tests have mostly been written in Python, and generally speaking, automated testing happens in the language you feel comfortable writings the test cases in. However tools like SOAPui(which also does REST), jmeter, rest-assured or K6 provide additional functionality.
We are using rest assured dsl mostly in company
How He created these animated diagrams?
Also need to mention about accessibility testing
what is the difference of load test and stress test?
Cool, keep it up!
Thank you
best one
Including the manager Mr Liban
Missing: end-to-end testing
Unfortunately the Indians at Abbott Laboratories lied on theirs tests.
I just rawdogg curl
+Chaos Engineering
❤❤❤❤
noice
Pansy Lodge