My Testing Thoughts

Despite having a small amount of storage on your local, do you need to do a task in a specific branch of git? Or, for a variety of reasons, you might only wish to clone a certain branch's files? Git, fortunately, allows the flexibility to accomplish this with single-branch parameter. What is the single-branch parameter in the git clone? It allows you to only fetch files from the specified branch and only tracks that branch without fetching other branches. git clone -b <branchname> — single-branch <remote-repo-url> Or git clone — branch <branchname> — single-branch <remote-repo-url>  

  Peter Drucker quoted “ You can't improve what you don't measure ” reminds us that measuring our progress is essential. It is especially important to measure what we do and what we measure too. Do read what I authored here: https://www.tavant.com/blog/top-metrics-measures-determine-test-automations-true-roi  

The Postman v10 release in Q3 of 2022 introduced the Postman CLI. If you are interested to know whether you should move from Newman to Postman CLI, please go through this: https://learning.postman.com/docs/postman-cli/postman-cli-overview Here is a direct comparison table: Postman CLI Vs Newman: https://learning.postman.com/docs/postman-cli/postman-cli-overview/#comparing-the-postman-cli-and-newman This should help to decide which command-line companion to use: https://learning.postman.com/docs/postman-cli/postman-cli-overview/#deciding-which-command-line-companion-to-use My 2 cents: Of course, Newman is not deprecated ( yet ) but I think it can be the case that the Postman team will work more actively on Postman CLI than Newman. If you are an existing Newman user, there is no push right now to move to Postman CLI. However, if you are just getting started with grokking backend automation with Postman then give it a shot to Postman CLI.

In today's world, where new automation test solutions are being released monthly, enterprises are looking for ways to expand and accelerate their software delivery processes. The key to success is choosing the right solution that balances your team’s skill sets and expertise and simultaneously meets your organization’s objectives. This blog details out the pros and cons of code-based vs. low-code/no-code test automation solutions. Author: Dheeraj Gambhir Blog Link Enjoyed reading this article? Please share the knowledge with your friends and colleagues.

QAOps - What is it? Is it a specialization or a new team role? – The answer is No.  QAOps is critical for teams that automate their Continuous Integration and Continuous Delivery (CI/CD) pipelines, as it focuses on speed without sacrificing quality. Head over to our recent blog that explores the various ways to implement. Enjoyed reading this article? Please share the knowledge with your friends and colleagues.

 A huge pain for SDETs is filling mock data to our automation test. PODAM is one such library that is easy to use, requires little to nothing set up, and auto-fills Java POJOs with data. It initializes a java object tree with random data, but you can also define a strategy or use attributes to decide the values that should be set (this makes it more powerful than other libraries like Java Faker, JFairy, etc.)   Read more here: https://mtedone.github.io/podam/index.html   Quick nice video: https://youtu.be/oaQSb-PxrrI Enjoyed reading this article? Please share the knowledge with your friends and colleagues.

  Pynt is a free API security solution that generates automated security tests based on your existing functional test collection within postman. It appeals to perform dynamic security testing covering all the OWASP API Top 10. More details:  https://www.postman.com/pynt-io/workspace/pynt/overview I tried and it looks promising. #pynt   #postman   #apisecurity   #testing   #security