1593379080
This talk was given as part of a live-stream with QA Babble, presented by Woodrow Mercer.
Testing Without the Safety Net - Tom McCrawley
Lots of people have heard of CI/CD, it almost seems to be the new normal. In reality though, few have taken steps onto this hallowed ground. In this talk I’ll talk you through some of the steps we took and processes we implemented to ensure quality when you’re testing without the safety net!
#ci/cd #qa #qa babble #testing #within
1593379080
This talk was given as part of a live-stream with QA Babble, presented by Woodrow Mercer.
Testing Without the Safety Net - Tom McCrawley
Lots of people have heard of CI/CD, it almost seems to be the new normal. In reality though, few have taken steps onto this hallowed ground. In this talk I’ll talk you through some of the steps we took and processes we implemented to ensure quality when you’re testing without the safety net!
#ci/cd #qa #qa babble #testing #within
1593359040
QA Babble is organised by Woodrow Mercer and presented on YouTube by Pusher. Testing Without the Safety Net - Tom McCrawley Lots of people have heard of CI/C
#testing #ci/cd #lunchtime sessions #qa
1589791867
CI/CD pipelines have long played a major role in speeding up the development and deployment of cloud-native apps. Cloud services like AWS lend themselves to more agile deployment through the services they offer as well as approaches such as Infrastructure as Code. There is no shortage of tools to help you manage your CI/CD pipeline as well.
While the majority of development teams have streamlined their pipelines to take full advantage of cloud-native features, there is still so much that can be done to refine CI/CD even further. The entire pipeline can now be built as code and managed either via Git as a single source of truth or by using visual tools to help guide the process.
The entire process can be fully automated. Even better, it can be made serverless, which allows the CI/CD pipeline to operate with immense efficiency. Git branches can even be utilized as a base for multiple pipelines. Thanks to the three tools from Amazon; AWS CodeCommit, AWS CodeBuild, and AWS CodeDeploy, serverless CI/CD on the AWS cloud is now easy to set up.
#aws #aws codebuild #aws codecommit #aws codedeploy #cd #cd pipeline #ci #ci/cd processes #ci/cd workflow #serverless
1599859380
Nowadays API testing is an integral part of testing. There are a lot of tools like postman, insomnia, etc. There are many articles that ask what is API, What is API testing, but the problem is How to do API testing? What I need to validate.
Note: In this article, I am going to use postman assertions for all the examples since it is the most popular tool. But this article is not intended only for the postman tool.
Let’s directly jump to the topic.
Let’s consider you have an API endpoint example http://dzone.com/getuserDetails/{{username}} when you send the get request to that URL it returns the JSON response.
My API endpoint is http://dzone.com/getuserDetails/{{username}}
The response is in JSON format like below
JSON
{
"jobTitle": "string",
"userid": "string",
"phoneNumber": "string",
"password": "string",
"email": "user@example.com",
"firstName": "string",
"lastName": "string",
"userName": "string",
"country": "string",
"region": "string",
"city": "string",
"department": "string",
"userType": 0
}
In the JSON we can see there are properties and associated values.
Now, For example, if we need details of the user with the username ‘ganeshhegde’ we need to send a **GET **request to **http://dzone.com/getuserDetails/ganeshhegde **
Now there are two scenarios.
1. Valid Usecase: User is available in the database and it returns user details with status code 200
2. Invalid Usecase: User is Unavailable/Invalid user in this case it returns status with code 404 with not found message.
#tutorial #performance #api #test automation #api testing #testing and qa #application programming interface #testing as a service #testing tutorial #api test
1591868664
Hello guys, this is a short blog on how to setup a maven project in karate DSL and small introduction to it’s directory and file structure. So let’s start with,
#api testing #quality assessment (qa) #testing #automation testing #qa #test automation #testing skills