Thanks for sharing Daniel, really good points you mentioned and I loved them. The last point (don't reuse the test data) was not very clear to me though. I'd be happy if you can explain a bit more or you may even want to create another video about handling the test data :) Thx in advance.
Hi Serkan, glad you liked the video. With don't re-use test data I mean that once you "used" or changed the initial data it's not the same anymore and the next time you execute the test with the changed test data the result will be different. Here is a simple example: 1. Imagine you have a username and password as test data and the user has some more attributes e.g. has user profile with image and more information. You import the test data to the db and then you sign up to your service. Then you change the data on the user profile or you change the username and password. Now the test data has changed, is used for the specific test run. The next time you want to perform the same test with the expected result, you might get a different result, because of the changed data. Imagine you execute a test script, the script expects the data to be in the exact format otherwise the test is failing. In order to re-use the data, you need to make sure to reset the data to the initial state at the end of your testing activities. This is time consuming and depending on the technology stack it can be challenging. It might be better to delete the data complete and start with a fresh set for the next run. Therefore, it might be worth to invest some time to create a test data set. The data set contains all kinds of variations of data you need for your testing. In best case you save the data in a database that has the same structure as the application. You can import the test data before each test run with a script and at the end of the test run, just wipe the DB. But keep in mind, this takes time to setup and to maintain. Hope it's clearer now. And thanks for the content wish regarding test data. Noted it down.
Hello sir, how can we do a performance test for a mobile application in the stage environment? Can you recommend some resources related to this? I saw that jmeter is also used
Hi Uti Anm, mobile performance testing has 3 areas to look out for. 1. The app itself, there you can use profiling tools provided by the IDEs. 2. the mobile network. This is the hardest part to check. But you can make sure that your APIs react fast, but you can't really check this because its not in your hands. 3. The backend. Many apps rely on a backend, and this need to be tested for performance as well. Depending on the tech stack there are different tools to use, JMeter might be one option.
Point 3 could have a full set of videos all of its own. It's a fascinating topic. Point 4 as well 👍👍👍👍 PS. You still sound like you're recording the videos hiding from your mum under the stairs 😉
Hi, glad you liked the video. Maybe I will do an extra video on the topics. Regarding the voice, I am not hiding anywhere ☺️. I changed the room setup so that the sound is not like standing in a hallway. Second I speak slowly and this lowers my voice a bit😅 but I think its better than screaming to the camera, right ;)?
Thanks for sharing Daniel, really good points you mentioned and I loved them. The last point (don't reuse the test data) was not very clear to me though. I'd be happy if you can explain a bit more or you may even want to create another video about handling the test data :) Thx in advance.
Hi Serkan,
glad you liked the video. With don't re-use test data I mean that once you "used" or changed the initial data it's not the same anymore and the next time you execute the test with the changed test data the result will be different. Here is a simple example:
1. Imagine you have a username and password as test data and the user has some more attributes e.g. has user profile with image and more information. You import the test data to the db and then you sign up to your service. Then you change the data on the user profile or you change the username and password. Now the test data has changed, is used for the specific test run. The next time you want to perform the same test with the expected result, you might get a different result, because of the changed data. Imagine you execute a test script, the script expects the data to be in the exact format otherwise the test is failing.
In order to re-use the data, you need to make sure to reset the data to the initial state at the end of your testing activities. This is time consuming and depending on the technology stack it can be challenging. It might be better to delete the data complete and start with a fresh set for the next run.
Therefore, it might be worth to invest some time to create a test data set. The data set contains all kinds of variations of data you need for your testing. In best case you save the data in a database that has the same structure as the application. You can import the test data before each test run with a script and at the end of the test run, just wipe the DB.
But keep in mind, this takes time to setup and to maintain.
Hope it's clearer now. And thanks for the content wish regarding test data. Noted it down.
@@DanielKnott Thanks a bunch for the detailed reply. Appreciated :) I'll take it with me.
Regarding test data the answer could also be "it depends" 😀
Hello sir, how can we do a performance test for a mobile application in the stage environment? Can you recommend some resources related to this? I saw that jmeter is also used
Hi Uti Anm, mobile performance testing has 3 areas to look out for. 1. The app itself, there you can use profiling tools provided by the IDEs. 2. the mobile network. This is the hardest part to check. But you can make sure that your APIs react fast, but you can't really check this because its not in your hands. 3. The backend. Many apps rely on a backend, and this need to be tested for performance as well. Depending on the tech stack there are different tools to use, JMeter might be one option.
@@DanielKnott Can you give some resources about this topic?
thanks for sharing
I hope its helpful.
Point 3 could have a full set of videos all of its own. It's a fascinating topic.
Point 4 as well 👍👍👍👍
PS. You still sound like you're recording the videos hiding from your mum under the stairs 😉
Hi,
glad you liked the video. Maybe I will do an extra video on the topics. Regarding the voice, I am not hiding anywhere ☺️. I changed the room setup so that the sound is not like standing in a hallway. Second I speak slowly and this lowers my voice a bit😅 but I think its better than screaming to the camera, right ;)?
@@DanielKnott yeah makes a change from the usual TH-camrs.... Keep up the good work.
(3) Automate everything!!11EINSELF!11! And of course within a day - should not be so complicated, ey? 😀
Ad always 😜