Test Environment Setup Example by SmartBear









Comments

Post a Comment

Popular posts from this blog

My review of EuroSTAR 2015 - Maastrict

Image
There are lot of great talks in EuroSTAR 2015.  I was really enjoy it, as well as the city Maastricht. Tidy, charming city with history, gourmet and exclusive shopping :) There are a few hot words into my ears. Autonomous management , self steer group.  DevOps is all about communication, collaboration, transparency.   Always start with WHY, follow with WHAT then HOW Continuous learning is the way to survival for tester.   Dedicate team, Automation in Agile.  Small team with B ig goal, leads to -> disruptive .  ************************************************************************** DevOps: My feel of DevOps is Collabration and Communcation.  To achieve efficiency, TA should be communication with different parities, get the needs from them ,and make the things happen. Open mind and fearless. [TU4].  Continuous Delivery means Continuous  Testing , but not means Continuous  Deployment  [TU4]. Communication ...
Read more

读书笔记 - Seven Tips For Making Better Presentations

 https://ericjacobsononmanagement.blogspot.com/2023/01/seven-tips-for-making-better.html Succinct stories that illicit emotional response are great hooks. Vary your voice to capture attention: modulate volume, rate, pitch, pace, and tone. Comparisons and analogies are powerful. Ask questions, such as, “What does what I’m sharing remind you of?” Use the questions to help your audience, smell, or sense what you’re describing. Repetition builds retention. State your most important point more than once. Move while you present. Make eye contact, a true show of courage. It’s a vital connection. If you don’t meet your audiences’ gaze, they are not likely to believe you. Pause occasionally to let all the great information you just said sink in. Add pictures and quotes into your presentations.
Read more

[读书笔记] The 16-point checklist for GitOps success

https://www.cncf.io/blog/2022/07/08/the-16-point-checklist-for-gitops-success/   We have adopted Kubernetes for container and infrastructure management :  -- Done  We have documented a clear workflow between Application Development teams and the Platform team :  -- Not ready We have trained teams on the new workflows and tooling :   --  Not ready We have identified which changes can be automatically deployed to production, and which require a manual pull request :   --  Not ready We have declared everything in Git (this includes applications, infrastructure, networking, and configuration) :   --  Part Ready We have decided on an initial structure for our Git repositories   --   Part Ready We have selected the appropriate tooling that makes up our GitOps pipeline (Flux, Helm, Flagger, etc) :   --  Done  We have connected GitOps toolings like Flux, Helm, and Kustomize to our Git repos...
Read more