Group Details Private

Global Moderators

Forum wide moderators

RE: Automatizar testes com Selenium utilizando C# é preciso ter um nível avançado de conhecimento na linguagem?

Não se preocupe com a quantidade de conhecimento para fazer automação. Se preocupe em adquirir conhecimento para resolver os problemas no processo. Senão o processo vai ser doloroso…

posted in Geral
Convince Your Boss to Send You to SmartBear Connect

Need a little help convincing your manager to allow you attend SmartBear Connect? No sweat! We have a few key points for you to express during your conversation with your manager when you ask for…

posted in Feed de Blogs e Posts
Build a docker image for your protractor automation

Hey guys, today I will post about an example of Docker file where you can run your protractor automation in a Docker container on firefox and chrome. You will need to have the known hosts and the public key from github to be able to clone the repository and run the automation. Also you need […]

posted in Feed de Blogs e Posts
[object Object]

This is another post in our Code Health series. A version of this post originally appeared in Google bathrooms worldwide as a Google Testing on the Toilet episode. You can download a printer-friendly version to display in your office.

By Tom O’Neill

Code reviews can slow down an individual code change, but they’re also an opportunity to improve your code and learn from another intelligent, experienced engineer. How can you get the most out of them?Aim to get most of your changes approved in the first round of review, with only minor comments. If your code reviews frequently require multiple rounds of comments, these tips can save you time.
Spend your reviewers’ time wisely—it’s a limited resource. If they’re catching issues that you could easily have caught yourself, you’re lowering the overall productivity of your team.Before you send out the code review:

  • Re-evaluate your code: Don’t just send the review out as soon as the tests pass. Step back and try to rethink the whole thing—can the design be cleaned up? Especially if it’s late in the day, see if a better approach occurs to you the next morning. Although this step might slow down an individual code change, it will result long-term in greater average throughput.
  • Consider an informal design discussion: If there’s something you’re not sure about, pair program, talk face-to-face, or send an early diff and ask for a “pre-review” of the overall design.
  • Self-review the change: Try to look at the code as critically as possible from the standpoint of someone who doesn’t know anything about it. Your code review tool can give you a radically different view of your code than the IDE. This can easily save you a round trip.
  • Make the diff easy to understand: Multiple changes at once make the code harder to review. When you self-review, look for simple changes that reduce the size of the diff. For example, save significant refactoring or formatting changes for another code review.
  • Don’t hide important info in the submit message: Put it in the code as well. Someone reading the code later is unlikely to look at the submit message.

When you’re addressing code review comments:

  • Re-evaluate your code after addressing non-trivial comments: Take a step back and really look at the code with fresh eyes. Once you’ve made one set of changes, you can often find additional improvements that are enabled or suggested by those changes. Just as with any refactoring, it may take several steps to reach the best design.
  • Understand why the reviewer made each comment: If you don’t understand the reasoning behind a comment, don’t just make the change—seek out the reviewer and learn something new.
  • Answer the reviewer’s questions in the code: Don’t just reply—make the code easier to understand (e.g., improve a variable name, change a boolean to an enum) or add a comment. Someone else is going to have the same question later on.

posted in Feed de Blogs e Posts
Executando testes com Protractor e Chrome em modo headless

Aprenda a utilizar este novo recurso disponível na versão 59 do navegador Google Chrome Na mais nova versão do Google Chrome (59 na data de publicação deste post) é possível executar testes automatizados em modo headless, o que pode ser uma vantagem para a execução de testes de forma mais rápida, por exemplo. Outra vantagem da … Continue lendo Executando testes com Protractor e Chrome em modo headless

posted in Feed de Blogs e Posts
Are You a Ready! API or TestComplete User? Check out what SmartBear Connect Would Look Like For You

Our first annual user conference, SmartBear Connect, comes to Boston September 12-13. This jam-packed event will bring together the world’s testing, development, and technology communities for:…

posted in Feed de Blogs e Posts
RE: Automatizando testes de APIs Rest com Postman e Newman

@Alan-Schveitzer Massa d+ \o/

Achei interessante e uma boa opção para quem está acostumado apenas com SoapUI


posted in Artigos e Tutoriais
Testcast – QA Market around the world

Hello everyone, I participated in a Podcast called TestCast We talked about our different experiences in QA Market around the world. Sadly, the podcast is 100% in Portuguese with no transcription.

posted in Feed de Blogs e Posts
Testes de regressão visual com Protractor e Applitools

Como testes automatizados a nível visual podem ajudar ainda mais na entrega de softwares de qualidade Fazia tempo que eu não publicava conteúdo novo aqui no blog, então aí vai um video novinho sobre testes de regressão visual com Protractor e Applitools. Espero que gostem! Em um próximo post pretendo demonstrar como configurar o Protractor para … Continue lendo Testes de regressão visual com Protractor e Applitools

posted in Feed de Blogs e Posts
What’s Next for the Software Testing Industry? Let’s Find Out.

We are happy to announce the launch of SmartBear’s first annual software testing survey! With this survey, we aim to define existing industry benchmarks and discover emerging trends and challenges…

posted in Feed de Blogs e Posts

Looks like your connection to Agile Testers was lost, please wait while we try to reconnect.