From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.
Can test automation replace human testers (Week 7)
From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.
Can test automation replace human testers (Week 7)
From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.
Can test automation replace human testers (Week 7)
From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.
Can test automation replace human testers (Week 7)
From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.
Can test automation replace human testers (Week 7)
From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.
Can test automation replace human testers (Week 7)
From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.
Can test automation replace human testers (Week 7)
From the blog Table of Code by Andon S and used with permission of the author. All other rights reserved by the author.
Week 7 – “9 Ways to Quickly Improve Your Writing Skills as a Software Tester”
Reading up on tips is always interesting to me. This week I read about some ways to improve your writing skills as a software tester. As a tester, you spend a lot of your time documenting; whether it’s to keep track of your findings personally, emailing co-workers, or professional documentation. The blog this week was written by Renuka K, a software tester that has 11+ years of experience. She discusses how being grammatically correct is extremely important for QA people. To start off, she gave an example of a small portion of two resumes saying the same thing. One of the resumes was grammatically correct, while the other was not. Although the two resumes had the same exact information, one of them seemed like an extremely better candidate for the position. Renuka stresses how important it is to be grammatically correct, but as a tester you don’t always need to speak so technical. There are appropriate and inappropriate times to be formal. For example, if you are sending an email to a fellow co-worker, you don’t nessacarily need to make it sound so professional. It’s okay to be friendly and non-professional sometimes. However, you need to make sure you are professional when necessary. Whenever you are dealing with a customer or documenting something that a customer will see; you need to be professional and grammatically correct. Some of the tips she shared that can help a software tester be a better writer are;
- Knowing your audience
- Read!!! (to write well you must learn to read well)
- Format your work to make it appealing to the eye
- Keep it simple
- Use an active voice
- Review and edit before submitting
- Practice every day
These tips were very helpful to me; not just in testing but anything I may choose to do. It is very important to keep in mind the quality of what you are writing as a tester, not just how fast you get it done. It is always better to have less of something exceptional then more of something mediocre.
From the blog CS@Worcester – Alex's Comp Sci Blog by alexsblog13 and used with permission of the author. All other rights reserved by the author.
Ultra Code 2016-11-05 12:37:00
Ankit
Week-7
Test Automation Language
Community management filed all the notifications for all the tester for the quater.lately is seems whenever you turn on the radio, tv or looked at the newspaper flyer, you can’t avoid the back to school sals. I notice you explicitly sidestep this question in your article, but generally, the compiled languages have much more powerful capabilities that the scripted languages do not exception handling, multithreading, synchronization, namespaces to manage complexity, XML support. I struggled with Ruby on a legacy project for months. No, Ruby doesn’t even come close to doing what I needed it to do, but more on that below.
From extensive technical discussions on what is possible with Python, I think it’s close, but not quite there, and it’s definitely a poor choice for a large, complex project.
Generally, scripting languages are widely used for “test automation” but their limited capabilities restrict them to an outmoded understanding of what that automation is all about and where it brings business value – really, the answer to the question “Why are we doing this?”
C or C++ can probably do it, but it’s been a while since I’ve used those languages. Java can do it, too, if you don’t need realtime, but my preference is C# which is more modern, better-designed, much better libraries, and more OO than Java.
From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.