Testando Graphql operations com Jest e apollo client
Artigos e Tutoriais2
Simular LongPress do hammer.js
Emular automação em com BD oracle
Problemas ao testar fluxo de compra com capybara + site prism
CTFL-AT: Simulado para a prova
[Pós Graduação] Recomendações UNICIV
Treinamento e Eventos7
ParserError: Failed to parser , alguem sabe como resolver?
Implementar automação para mobile. Qual ferramenta escolheriam?
[Dúvida] - Inspecionar tagbox
VAGA: Testador de Software
Vaga - Automação de Testes - São Paulo (Metrô Republica)
Katalon - Preciso aula particular via skype
Page Objects Pattern e Por Quê Utilizá-lo nos Seus Testes de UI (User Interface)
Artigos e Tutoriais7
Um Nub no selenium IDE
Artigos e Tutoriais4
Artigos e Tutoriais1
Preciso clicar usando xpath
[Dúvida] - Expect(page)
TDD e BDD Juntos?
Matcher Equivalente ao AsserEquals do JUnit
Exploratory Testing Clean Recon Live Example
TLDR: clean recon - using the app to provide knowledge about the app
Using The Pulper v 1.2 I recorded a live recon session to try and create an example of note taking, model building, risk identification and next action identification.
You can repeat the exercise for yourself and see how you get on.
Using The Pulper v 1.2 I performed a live recon session.
I described it as a ‘Clean’ recon. By which I mean:
- little, to no, prior planning* based purely on information provided by the app* no tool support* unstructured text file for note takingOther recon types include:
- Mental* Biased/Prompted (Mnemonic, Template, Goal, etc.)* Tool Assisted
The note taking makes a difference.
Plain Text allows me to write in any order, with no structure.
Mindmap enforces some structure and can lead to a physical structural model of the app. Mind-map is often good for Prompted recons.
I do other types of recons to build a rich model of the application. I do not rely on a single recon.
I tend to start with a ‘clean’ recon.
Lessons Learned and Actions Identified
- Even a ‘read only app’ has complexity* Particularly around data oracles* Even in a recon we can spot bugs.I need to identify:
- how to compare pages of data in the app* how to compare data on different pages within the appI identified classes of tools I can use to support my testing:
- link checkers* html validatorsBut I recognise that these test the ‘syntax’ or ‘structure’ but not the semantics of the app e.g. data is rendered correctly, but is the correct data rendered?
I used version 1.2 of The Pulper from https://github.com/eviltester/TestingApp/releases
I recommend this, as an exercise for you. Or pick any app you are working on.
You can perform a ‘clean’ recon, even on apps you know well. I programmed The Pulper, I was still able to take a fresh look at it in the recon and I gained valued by doing so.
- Download version 1.2 of The Pulper from https://github.com/eviltester/TestingApp/releases* Perform a clean recon* Reflect on your notes* What did you find?* What did you learn?* What risks did you identify?* Did you spot any bugs?* What will you do next?* What tools do you have to research?