Power Tester
Power Tester
  • 110
  • 42 587
#56 Test Logging: Mapping parallel run log statements to test case names for better traceability.
GitHub: github.com/PramodKumarYadav/zero
Goal:
In this video, we see how to map each log statement to its corresponding calling test name.
Objective:
- A test can call multiple entities to get values for the test and this approach shows us how we can map the logs from those entities to its caller test name.
Next steps:
-
Переглядів: 388

Відео

#55 Test Monitoring: Creating meaningful dashboards on Kibana & making testing transparent to others
Переглядів 265Рік тому
GitHub: github.com/PramodKumarYadav/zero Goal: In this video, we show how you can convert the information you published on elastic to visual meaningful graphs. Objective: - We will create two graphs (a heatmap and a line graph) to show how you can see test trends and test trigger trends. Next steps: -
#54 Test Run Extension: To mimic beforeTestRun and afterTestRun methods - that dont exist in Junit5.
Переглядів 92Рік тому
GitHub: github.com/PramodKumarYadav/zero Goal: In this video we learn how to create custom functionality to mimic beforeTestRun and afterTestRun methods that dont exist in Junit5 out of the box. Objective: - To allow for use cases where we want to do certain actions at the run level only. Next steps: -
#53 Extensions Auto Registering: Automatic registering of common Extensions for test classes.
Переглядів 149Рік тому
GitHub: github.com/PramodKumarYadav/zero Goal: In this video we learn how we can register extensions automatically without having to use @ExtendWith annotation to declaratively register extensions in Junit5. Objective: - Make using extensions more human error proof and clean. Next steps: -
#32 Health checks and how they can make your CI pipelines more efficient
Переглядів 258Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: Health checks and how they can make your CI pipelines more efficient Objective: - Show how to use health checks to make CI pipelines more efficient. Next steps: - Show how to parse JSON array responses.
#31 How to optimise log responses to log only for failed tests
Переглядів 63Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: Make logging efficient. Objective: - Show how to optimise log responses to log only for failed tests Next steps: - Cover topic of health checks.
#30 How to skip sensitive information from accidental logging on console
Переглядів 122Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: Skip sensitive information from accidental logging on console Objective: - Show how to skip headers that contains tokens and authorization inputs. Next steps: - Optimize overall log responses.
#29 Creating singleton auth token class to reuse auth tokens across tests
Переглядів 262Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: Make usage of tokens more efficient. Objective: - Create a singleton pattern for auth tokens. Next steps: - Hide secrets from logging.
#28 Creating a TokenFactory to provide tokens for different scopes
Переглядів 100Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: Handle tokens for different scopes efficiently. Objective: - Creating a TokenFactory to provide tokens for different scopes Next steps: - Create a singleton pattern for auth tokens.
#27 Make API methods scope agnostic to test for different scopes and user roles
Переглядів 75Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: Allow for testing same APIs with different scopes and user roles (for both positive/negative testing) Objective: - Make API methods scope agnostic to test for different scopes and user roles Next steps: - Create a AuthFactory to get auth tokens for different scopes.
#25 @JsonIgnoreProperties annotation: To ignore unknown fields while deserialising response
Переглядів 289Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: Ignore unknown fields to parse only relevant fields while deserialising response. Objective: - Ignore unknown fields to parse only relevant fields while deserialising response using JsonIgnore properties annotation Next steps: - Fix formatting issues.
#26 Fix code formatting issues in local as reported in CI.
Переглядів 69Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: - Fix code formatting issues in local as reported in CI. Objective: - Fix code formatting issues in local. Next steps: - Make APIs scope agnostic.
#24 Refactor Schemas to move them to another directory.
Переглядів 36Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: Refactor and restructure Schema files in their own directory. Objective: - Refactor Schemas to move them to a directory. Next steps: - Use @JSON ignore annotation to skip unwanted fields from deserialisation.
#23 How to do JSON schema validation using RestAssured.
Переглядів 190Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: Add JSON schema validation in tests. Objective: - Show how to do JSON schema validation. Next steps: - Refactor schema path to pick schema from a directory.
#22 Fluent assertions for both common and specific API responses
Переглядів 82Рік тому
GitHub: github.com/PramodKumarYadav/restpro Goal: - Refactor assert classes so that user can do all assertions in one fluent method chain. Objective: - Refactor Verify Response assert class and child assert classes, so that user can do all assertions in one fluent method chain. Next steps: - Add method for doing JSON Schema validation.
#21 Creating API specific Assertion class
Переглядів 61Рік тому
#21 Creating API specific Assertion class
#20 Creating common Response Assertion class
Переглядів 70Рік тому
#20 Creating common Response Assertion class
#19 Why using shared static fields inside tests is a bad idea
Переглядів 58Рік тому
#19 Why using shared static fields inside tests is a bad idea
#18 Adding setup and teardown methods to tests
Переглядів 77Рік тому
#18 Adding setup and teardown methods to tests
#17 Refactor and separate config from code
Переглядів 104Рік тому
#17 Refactor and separate config from code
#16 Refactoring common request headers and request items into a BaseSpec class
Переглядів 73Рік тому
#16 Refactoring common request headers and request items into a BaseSpec class
#15 Add a very basic AuthToken class to provide auth tokens to API methods
Переглядів 126Рік тому
#15 Add a very basic AuthToken class to provide auth tokens to API methods
#14 Demonstrate GitHub project tasks workflow using "Extend Test with Setup Class" as an example
Переглядів 83Рік тому
#14 Demonstrate GitHub project tasks workflow using "Extend Test with Setup Class" as an example
#13 @JsonInclude annotation: To skip null fields and only include non null fields in request body
Переглядів 261Рік тому
#13 @JsonInclude annotation: To skip null fields and only include non null fields in request body
#12 @Accessors annotation: To mutate and do method chaining on existing objects.
Переглядів 96Рік тому
#12 @Accessors annotation: To mutate and do method chaining on existing objects.
#11 @Builder annotation: To do method chaining and write readable tests and methods.
Переглядів 146Рік тому
#11 @Builder annotation: To do method chaining and write readable tests and methods.
#10 Refactoring tests to separate Request, Response and API in their own classes.
Переглядів 213Рік тому
#10 Refactoring tests to separate Request, Response and API in their own classes.
#9 Writing some very basic RestAssured Tests
Переглядів 132Рік тому
#9 Writing some very basic RestAssured Tests
#8 Refactoring http request to make it work for any test environment
Переглядів 161Рік тому
#8 Refactoring http request to make it work for any test environment
#7 Exploring application under test (restful booker) using http client before automating it
Переглядів 664Рік тому
#7 Exploring application under test (restful booker) using http client before automating it

КОМЕНТАРІ

  • @VacuSteel
    @VacuSteel Місяць тому

    Do you have email how can I chat with you

  • @roshnray6566
    @roshnray6566 4 місяці тому

    Thanks sir for all the playlists

  • @DreamEatCode
    @DreamEatCode 4 місяці тому

    I am getting build issues 😢

  • @67ravii
    @67ravii 5 місяців тому

    14th video should be at 16th position actually.

  • @akshaykachare7805
    @akshaykachare7805 7 місяців тому

    How to do parallelism in cucumber to run feature file or scenarios in parallel

    • @powertester5596
      @powertester5596 7 місяців тому

      I dont like Cucumber and dont use it but know that last time I checked, it does support running feature files in parallel. This video is not what you are looking for that use case.

  • @pavanchawthay2150
    @pavanchawthay2150 7 місяців тому

    This one is currently not in your repo!!

  • @rajkumarwinc9372
    @rajkumarwinc9372 10 місяців тому

    Hi, thanks for your valuable stuff... I have implemented the same in my project but parallelism is not working as expected, i have configured junit-profile.properites and placed in src/main/resources folder. Could you please give me any clue 🗝️

    • @powertester5596
      @powertester5596 10 місяців тому

      Are you using junit5?

    • @rajkumarwinc9372
      @rajkumarwinc9372 10 місяців тому

      ​@@powertester5596I'm using junit-jupiter 5.8.2 And using below configuration junit.jupiter.execution.parallel.enabled = true junit.jupiter.execution.parallel.mode.default = concurrent junit.jupiter.execution.parallel.mode.classes.default = concurrent

  • @AdarshSingh-go5ht
    @AdarshSingh-go5ht 11 місяців тому

    Is there a way to format only the line of code which I have added in the existing java file ? I don't want to reformat the full class.

    • @powertester5596
      @powertester5596 11 місяців тому

      Formaters don’t work like that and for good reason. Imagine you already have un formatted code committed in the repository and your team introduces formatting later. If you touch one line in the file, you would still want the whole file to be formatted. I am curious why would you only want it to run only on the changed lines and not full file?

    • @AdarshSingh-go5ht
      @AdarshSingh-go5ht 11 місяців тому

      @@powertester5596 this is because formatting whole file will unnecessary reflect the changes (if lines of code are more) in PR and it's kind of overwork if I'm only concerned about my changes and extra work for reviewer too.

    • @powertester5596
      @powertester5596 11 місяців тому

      @@AdarshSingh-go5ht the standard and recommended is to one time format the whole project and create a PR only for formatting changes. Once it is done, the problem you mention will never happen again.

  • @shitalmalviya9796
    @shitalmalviya9796 11 місяців тому

    Hello Pramod,when we want to pass any variable value from cmd we need to mentioned in pom ex. if i am using .properties file then in pom either i included resources tag to allow filtering or mention that variable in property tag. here, how maven is able to directly map our TEST_ENV from conf file to -DTEST_ENV

    • @powertester5596
      @powertester5596 11 місяців тому

      Hi Shital. Maven is just one of the ways in which you can work with env. There are other solutions like dotenv and typesafe (that we used) that can set/get env variables for the project. Cheers!

    • @shitalmalviya9796
      @shitalmalviya9796 11 місяців тому

      @@powertester5596 What i mean to ask in maven with property file we have to explicitly mention if we want to allow runtime modification to our variable. but when we use typesafe all the variable mentioned under reference conf file can be modify from cmd without explicitly mentioning it anyhwere ? just want to confirm it ...

    • @powertester5596
      @powertester5596 11 місяців тому

      @@shitalmalviya9796 the variables are specified in .conf files under resources repository. If that’s what you mean?

  • @shitalmalviya9796
    @shitalmalviya9796 11 місяців тому

    Hi Pramod , even after placing GIT_CRYPT_key in secrets i am getting same error - Error: ./git-crypt-key: not a valid git-crypt key file I created it with the latest git- crypt version

    • @powertester5596
      @powertester5596 11 місяців тому

      You don’t have to create a ID. You have to use the ID provided. Can you try again just using it ? I will also make updates in my framework to see if I can make working with git crypt easier or even get rid of it :)

    • @shitalmalviya9796
      @shitalmalviya9796 11 місяців тому

      @@powertester5596 Hello Pramod, it worked for me thanks. Yes let us know a different approach as getting git-cryt on a company vm is a challenge and I cant use key created outside company network.

  • @MaheshJoshi_wellington
    @MaheshJoshi_wellington 11 місяців тому

    Really looking forward to playwright series with typescript/JavaScript from you

    • @powertester5596
      @powertester5596 11 місяців тому

      I look forward to creating it too :-).

  • @MaheshJoshi_wellington
    @MaheshJoshi_wellington 11 місяців тому

    this is gem sir Thank you !

  • @MaheshJoshi_wellington
    @MaheshJoshi_wellington 11 місяців тому

    This is amazing ! subscribed ! sir thank you

  • @avishekbehera
    @avishekbehera 11 місяців тому

    Thanks, Pramod for this amazing and accurate way of getting test execution time. The more I watch the playlist the more love I have for JUnit ❤. Did you miss to add the logic to remove the thread ? Probaby in TestSetup we can add a step?

    • @powertester5596
      @powertester5596 11 місяців тому

      I probably forgot to remove the thread if you noticed it :-). Yes, you are right we should remove it :-).

    • @avishekbehera
      @avishekbehera 11 місяців тому

      @@powertester5596 That's fine, good part is , your entire series is made with so details and spontaneous way that anyone watches would be able to get the core of it. I would urge you to keep making contents like this whenever time permits. Kudos.

    • @powertester5596
      @powertester5596 11 місяців тому

      @@avishekbehera Thanks buddy! Appreciate your kind words. I am currently building a powerhouse of feature items to share in Playwright :-). Maybe in a few months when work is more relaxed I intend to create one of the best series in playwright out there :-).

  • @avishekbehera
    @avishekbehera 11 місяців тому

    Hey Pramod, brilliant one. I thought about the solution when we worked together back then but never got to dig deeper. Self type or can we call it Self referential type to be precise? New for me, and shout out to Kasia ( If you ever get to read this comment :) ) By the way, I am addictively going through this series with better focus and things look relatable and easier to understand as we had something similar at work. Kudos to your efforts in making this series 🙌🏻

    • @powertester5596
      @powertester5596 11 місяців тому

      Thanks buddy :-). Glad you liked it. Real credit goes to Kasia for introducing me to this idea :-). It made everything so clean in API test design :-)

  • @Swekar14
    @Swekar14 Рік тому

    This is very informative! Thank you. One important thing you’ve taught us is that no other tutorial is better than tools own documentation. Best place to look at. ❤

  • @danjelhysenaj4859
    @danjelhysenaj4859 Рік тому

    Keep up with good work my friend. :)

  • @virajedirisinghe-z1o
    @virajedirisinghe-z1o Рік тому

    Thank you Pramod. Very valuable content

  • @anirudhgupta3059
    @anirudhgupta3059 Рік тому

    Hi Pramod I am using a git crypt config file in my github project & running through jenkins but facing same issue where file is not getting decrypted, do you have a similar steps to add a secret in Jenkins instead of Github actions? TIA

    • @powertester5596
      @powertester5596 Рік тому

      Hi Anirudh, you can use the information in the GitHub action plugin to unlock the files in CI. Here is the repo: github.com/sliteteam/github-action-git-crypt-unlock/tree/master Basically you need to first install git crypt in CI using bash. The dockerfile setup contains that step. i.e. "apk --update add git-crypt git-lfs" And once you have git crypt installed in CI, you can run the entrypoint.sh script as it is available in the root of the above project. github.com/sliteteam/github-action-git-crypt-unlock/blob/master/entrypoint.sh Do remember to add a secret in jenkins with name "GIT_CRYPT_KEY" since it is used in the entrypoint.sh file. Hope it helps.

  • @avishekbehera
    @avishekbehera Рік тому

    Thank you Pramod. This is very insightful and pretty flawless to work with. I found datadog to be overwhelming a bit but again the dashboard can be built with any of similar tool. I would like to hear your thoughts compared to DD. Very interesting topic though.

    • @powertester5596
      @powertester5596 Рік тому

      Thanks buddy :-). I also prefer elastic and Kibana over datadog. I personally found ease of use and flexibility in Kibana to be much better than datadog.

  • @praveenkumar-r8l8n
    @praveenkumar-r8l8n Рік тому

    Hi Sir, I am having one query. Here you have created one branch in the local and then created a PR to merge it in the remote main branch right? So the local main branch doesn't have that .gitignore file.. Unless and until we have taken the latest pull?

    • @powertester5596
      @powertester5596 Рік тому

      Hi there, yes if you don't see the file in the local main branch you can pull it from the main remote branch. More importantly, I sense from your question that you can use some help on how Git works. Maybe try watching some good tutorials on it? P.S: Here is a short tutorial from one of my favorite authors (but feel free to learn it from anywhere you like :)): ua-cam.com/play/PL-osiE80TeTuRUfjRe54Eea17-YfnOOAx.html

    • @praveenkumar-r8l8n
      @praveenkumar-r8l8n Рік тому

      @@powertester5596 Yea sure sir, thanks a lot for the confirmation! I'll check those tutorials..

  • @Unknown-ed1it
    @Unknown-ed1it Рік тому

    com.typesafe.config.ConfigException$Missing: merge of system properties,application.conf @ file:/C:/Users/suris/zerorepo/restpro/target/classes/application.conf: 1,system properties,choices.conf @ file:/C:/Users/suris/zerorepo/restpro/target/classes/choices.conf: 1,system properties,staging/test-data.conf @ file:/C:/Users/suris/zerorepo/restpro/target/classes/staging/test-data.conf: 1,system properties,staging/user-info.conf @ file:/C:/Users/suris/zerorepo/restpro/target/classes/staging/user-info.conf: 1: No configuration setting found for key 'BASE_URL'

  • @pritamsharma1831
    @pritamsharma1831 Рік тому

    it was good session

  • @douglasfugazi
    @douglasfugazi Рік тому

    I was looking for something like that. Thanks for sharing!!!

  • @durgaprasadmajji8057
    @durgaprasadmajji8057 Рік тому

    How it is taking authentication? Means username and password ?

    • @powertester5596
      @powertester5596 Рік тому

      If you see in GitHub you will find a class to provide request specification. It contains methods that provide both authenticated specification and non authenticated specification.

  • @МиколаПаславський-н9й

    You record video how to set logs for 17 mins?)

    • @powertester5596
      @powertester5596 Рік тому

      I know what you mean. I am still not the best when it comes to creating content :-). Sorry!

    • @avishekbehera
      @avishekbehera 11 місяців тому

      Oh well, I would love to see how you do it? Why not link a video of yours then?

  • @RuthvikAlladi
    @RuthvikAlladi Рік тому

    Sir withFallBack() is not adding non-existing values. It is throwing error to add the same property in parent config. So that it overrides.

    • @powertester5596
      @powertester5596 Рік тому

      Hmmm. That’s weird since the baseURL only exists in the environment repo and not in the parent file and it works. Maybe can you try with smaller config files with one or two fields to see where the issue is?

    • @RuthvikAlladi
      @RuthvikAlladi Рік тому

      ​​@@powertester5596Sir i have structured like. conf/env..properties conf/prod/env..properties conf/test/env..properties I have a key (ENV) in the first file which allows ENVIRONMENT enum. And in both test and prod environment files I have a key USER_NAME. When i tried to fetch USER_NAME then it was throwing an error as no key defined USER_NAME in file config/env..properties (Ignore .. if I add only one dot it is treating it as website and removing my comment)

    • @powertester5596
      @powertester5596 Рік тому

      @@RuthvikAlladi is the structure as you say with Conf ? Or is it resources/dev/file name.conf ? Note that the class I shared expect structure as stated in second one.

    • @RuthvikAlladi
      @RuthvikAlladi Рік тому

      @@powertester5596 sir I think there is a confusion. The structure i mentioned is folder structure. src/test/resources/config In that config folder i have 1 file and 2 folders. env. properties , prod(folder), test(folder) In both prod and test there is a file named env. properties. In config/env. properties i will mention the environment to choose and common properties In prod/env . properties and test/env. properties. There will be environment specific variables.

    • @powertester5596
      @powertester5596 Рік тому

      @@RuthvikAlladi I understand but there should not be folder inside config folder. The structure that the Java class deals with is resources/env-folder-name/files.Conf . Try changing like this and see if it works for you?

  • @kislayapant6119
    @kislayapant6119 Рік тому

    Great Video. Awesome content. There is very less content for QA out there on the internet as compared to devs. Sir keep it up , QA community requires more such video content. 😊

  • @kislayapant6119
    @kislayapant6119 Рік тому

    Hello Pramod, Need to ask do we need to watch the Project zero playlist first before starting with this playlist as you are using the base project as Project Zero.

    • @powertester5596
      @powertester5596 Рік тому

      Project zero contains most of the topics that are common to "any" test automation framework. If you watch it first you will get more insight on some of the common things we use here. That said, I don't think it should stop you from being productive with API testing if you don't watch it first. So whatever you like :).

    • @kislayapant6119
      @kislayapant6119 Рік тому

      @@powertester5596 thanks Pramod will watch the series post rest pro series. Thanks

  • @Swekar14
    @Swekar14 Рік тому

    Hey Pramod, have one question- my org uses Jenkins for CI and I create a docker image and run my tests within it, problem that I’m facing is that git-crypt unlock is not working actually and files are still encrypted even though on unlock there is no error. I use alpine image and install jre, git-crypt. May be if you could guide a way to unlock in jenkins or in a docker image would be helpful. Congratulations on your new role btw 🤓😀. TIA

    • @powertester5596
      @powertester5596 Рік тому

      Thanks Karan :-). This topic was actually in my todo list. I hope to find sometime soon to make a video on it. For now, I think there are 2 ways in which we can install git crypt. One of them should work for Linux machines. Would you like to give it a try?

    • @Swekar14
      @Swekar14 Рік тому

      @@powertester5596 yes installation is successful on docker image using apk add git-crypt and infact to troubleshoot I’m copying my key as well via Dockerfile usinf COPY command and trying to unlock, still it did not work 😅

    • @powertester5596
      @powertester5596 Рік тому

      @@Swekar14 : okay. To troubleshoot,see if you can go inside the container and ls to see if the copied file is present there or not. Do let me know what you see. This weekend is going to be super busy for me else would have tried this. I will still see if I can :-)

    • @Swekar14
      @Swekar14 Рік тому

      @@powertester5596 yes it is there! I was using alpine and thought to perform same on ubuntu image. While decrypting on ubuntu i found a git error saying “you are on a branch yet to be born and encrypted files not decrypted”. Tried after git init as well and same issue, seems git is preventing from decrypting due to branch issue.

    • @powertester5596
      @powertester5596 Рік тому

      @@Swekar14 : hmmm. This error indicates that the branch doesn’t exist. Maybe your main branch is named as master or vice versa?

  • @aravindmr6827
    @aravindmr6827 Рік тому

    Hello Pramod,just after seeing this video I had a situation in my project where I had to use jsonignoreproperties.Thank you for the info❤.I have a question,say for an endpoint I have to use this 2 additional fields which I will use to assert,but not for others.Is it okay to create a single response pojo including these fields ?will it fail during parallel run where it doesn’t require these additional fields?

    • @powertester5596
      @powertester5596 Рік тому

      I am glad it helped you. You can create assert for each response field using soft asserts and then for each test, only include the fields that you need to assert. Do let me know that helps solve your problem in hand?

    • @aravindmr6827
      @aravindmr6827 Рік тому

      @@powertester5596 Thank you for the quick reply.I am able to assert it,however the challenge I have is ,with the parallel run it fails(felt like a flakiness there,at time this gets passed ) but works perfectly for individual run

    • @powertester5596
      @powertester5596 Рік тому

      @@aravindmr6827 if your test fails on parallel run but not in sequence most probably you are using a static field that is changed by multiple tests. Don’t use static fields and your tests would run perfectly fine. I in-fact made a video on it that you can find in the same playlist.

    • @aravindmr6827
      @aravindmr6827 Рік тому

      @@powertester5596mmm..i haven’t used any static fields though

    • @powertester5596
      @powertester5596 Рік тому

      @@aravindmr6827 somewhere it is using a shared variable. That’s how parallel issues happen. If I could have had a look at your code I could have helped debug and fix it but workout looking at it it’s difficult to point to the root cause.

  • @ravichandola2081
    @ravichandola2081 Рік тому

    This is awesome pramod. Keep up the good work.

  • @mrwho9475
    @mrwho9475 Рік тому

    I have never seen such an detailed playlist covering almost everything with so much clean coding. Thank you so much.

  • @JuanSandoval-bq9oi
    @JuanSandoval-bq9oi Рік тому

    Hello, I find your videos very interesting, thank you very much for the information. One question, can Kibana and Elastic be used for free or do you have to pay to use them?

    • @powertester5596
      @powertester5596 Рік тому

      Thank you Juan :-). Elastic and Kibana are free if you want to install on your local machine/server. They also have a cloud paid version which is normally used by companies. You can also try it out for free for a week or two.

    • @JuanSandoval-bq9oi
      @JuanSandoval-bq9oi Рік тому

      @@powertester5596 Thanks!

  • @aravindmr6827
    @aravindmr6827 Рік тому

    Thank you for the info.Great piece of information.A quick question,say I have a pojo,to hit a certain endpoint i need all the 4 fields in the pojo and for another I need only 2 from the same.Is it a good practice to use the same pojo to hit both the endpoints and annotate with jsonignore? P.S- Appreciate if you could zoom a bit while recording..a humble suggestion,Thank you

    • @powertester5596
      @powertester5596 Рік тому

      If you are talking about input POJO body, then what you need is @JsonInclude(JsonInclude.Include.NON_NULL) For different endpoints you can then only set the fields that you want to set and others will be ignored. About zooming, I will try to keep in mind. Thanks for the input. I have a big monitor and needs a better solution for screen resolution.

    • @aravindmr6827
      @aravindmr6827 Рік тому

      @@powertester5596 Sorry my bad,I was referring to input body.Thanks for answering

  • @Swekar14
    @Swekar14 Рік тому

    This is super informative! Will surely implement in my office project!

  • @krishanuchakraborty3500
    @krishanuchakraborty3500 Рік тому

    Thanks Pramod, this is really helpful

  • @avishekbehera
    @avishekbehera Рік тому

    Amazing video. New things for me. 1- NIce use of Health check, makes good sense, having health check endpoint is easy , if not available we can demand for it 2- AQUA's powerful and beautiful HTTP capabilities, that can reside within codebase, so absolutely no need of any external documentation like swagger or postman. Thanks Pramod, good going. Lets proceed to next :)

    • @powertester5596
      @powertester5596 Рік тому

      Glad that you like it buddy :-). I am also going to make all our tests scope/role aware and our APIs as scope agnostic. If you recall all our APIs are currently tightly coupled to one role “say admin”. I will make all APIs as scope agnostic and then you can test same APIs based on different roles and thus different expected response codes per role (say 200 for admin and 403 for a guest user :-) )

    • @avishekbehera
      @avishekbehera Рік тому

      @@powertester5596 Good one, as developers too use generic error templates based on roles , so it would be easier and cleaner to have scope-agnostic implementation.

  • @vidhya821
    @vidhya821 Рік тому

    Looking forward to your content ☺️

  • @avishekbehera
    @avishekbehera Рік тому

    Good call Pramod, restful-broker is my go-to API playground, been using for quite sometime. Very simple, neat documentation and has all CRUD and Auth usecases too. Also, bonus point, it has some bugs too, which will also be good for learning ;) Curious to learn how you leverage Health check, Waiting for the next one :)

    • @powertester5596
      @powertester5596 Рік тому

      Thanks buddy :). Sure. I created another video on schema validation today. Hopefully in a day or two, will push the code of how to use health check in CI :). The video may come out a little later since I am yet to edit more videos from before but you would be able to pick the solution from GitHub :)

  • @AyyAppA_009
    @AyyAppA_009 Рік тому

    Thanks Pramod…Is aqua IDE is the paid version..?

    • @powertester5596
      @powertester5596 Рік тому

      Hello Ayyappa, it’s free (atleast for now). Not sure if IntelliJ plans to keep it free or paid in future but at this moment, it is free.

  • @avishekbehera
    @avishekbehera Рік тому

    Another great series in action ✌️. Thank you for taking time to layout the beautiful foundation and it's really a most demanded series. Happy to see this out 🙏

  • @vidhya821
    @vidhya821 Рік тому

    New SubUser 🙂

  • @Swekar14
    @Swekar14 Рік тому

    It’s just perfect

  • @LakshVince
    @LakshVince Рік тому

    Do you have any plan for personal coaching or can you share your email so I can solve my queries?

    • @powertester5596
      @powertester5596 Рік тому

      Hey there, at this moment due to time constraints, I have no plans to take personal coaching. Maybe in future. For now, you can ask relevant questions either here or on GitHub project. I will try to answer once in a while when I find time but cannot guarantee :-).

  • @automationneemo
    @automationneemo Рік тому

    The diagram is cool! Great work!

    • @powertester5596
      @powertester5596 Рік тому

      You can download it from GitHub project - drawings directory; if you like :-).

  • @aravindmr6827
    @aravindmr6827 Рік тому

    A neat briefing…A tiny request would be to release the rest of the videos ASAP as am setting up api test cases in my current organisation 😅.I guess this video would add value to the same.Request you to add the best practices for the UI part as well to have an understanding of how this works when this is used to set the state.Waiting for the rest of the series ❤

    • @powertester5596
      @powertester5596 Рік тому

      Sure Arvind. I have the recordings ready and just need some time to do minor editing before releasing. The GitHub project is already in a good state to clone through. If you put a watch on the repository you would be notified once I add more content to the repo. Cheers!

    • @aravindmr6827
      @aravindmr6827 Рік тому

      @@powertester5596 sure.Thank you

  • @SuperSuneel
    @SuperSuneel Рік тому

    A very good intro

  • @TestingMiniBytes
    @TestingMiniBytes Рік тому

    Wow !!

  • @AyyAppA_009
    @AyyAppA_009 Рік тому

    Thanks..very well explained