Por acaso tu já tentou colocar um breakpoint na segunda classe e verificar se o driver é instanciado novamente ou ele tenta usar a sessão atual e fecha no processo? Acho que pela estrutura que tu está usando seria o mais sensato…A minha duvida é, se tu criar duas classes independentes de teste, e rodar individual, funciona?
Detalhes do Grupo Particular
Forum wide moderators
Lista de Membros
Isso está suspeito, parece que tu está tentando fechar o driver o qual já parece estar fechado…Chegou a ver se está inicializando o driver e fechando na sequencia correta?
Não está dando algum “driver.close” e tentando fechar…e pq driver = null; ?
Uma duvida, a cada teste ele fecha o driver? Onde reinicializa ele dai…?
Depende muito do aplicativo que vai testar. Se o android tem fluxo diferentes do iOS, de nada adianta tentar reutilizar o que fez no iOS. Se os fluxo de navegação são compartilhados, Seria analisar sobre o elementos e diferenciar na config para executar. Usar appium é exatamente para reaproveitamento dos testes para ambas as plataformas. Sabemos que no mundo real as coisas pode ser complicadas, mas o que eu faria seria analisar os fluxos de navegação. Tendo isso em mãos fica visível se tu precisa dividir o código ou pode reaproveitar…
Chegou a dar uma olhada nesse link https://www.automatetheplanet.com/getting-started-appium-android-csharp/ ? Na verdade se jogar no google se acha materiais feitos esse ano até…
Mais um video de Talking About Testing Neste bate papo informal, Gabriel e eu discutimos refatoração sob a perspectiva de teste de software, baseado no livro Refactoring segunda edição, do Martin Fowler, com pitadas de Kent Beck. Enjoy! E que o refactoring esteja com você! ;P Anúncios
Writing a Chrome Extension is pretty easy (getting it in the Chrome Store is much harder!). In this post I describe the steps to handling if your extension is rejected.
I have now released two extensions to the Chrome Store.
Both were rejected.
For the same generic reasons.
Dear Developer, Your Google Chrome item, “…” did not comply with our policies and was removed from the Google Chrome Web Store. Your item did not comply with the following section of our policy:
Do not post repetitive content.
Do not attempt to change the placement of any Product in the store, or manipulate any Product ratings or reviews, by unauthorized means, such as fraudulent installs, paid or fake reviews or ratings, or offering incentives to rate Products.
Do not post an app if the primary functionality is to link to a website not owned by the developer posting the app.
Do not post an app where the primary functionality is to install or launch another app, theme, or extension. For example, you cannot post an app if its primary function is to launch a desktop app that the user has already installed. Another example of a disallowed practice would be to post a packaged app that just launches a website.
Your app must comply with Google’s Webmaster Quality Guidelines
If you’d like to re-submit your item, please make the appropriate changes to the item so that it complies with our policies, then re-publish it in your developer dashboard. Please reply to this email for issues regarding this item removal.
My extensions did none of this.
The Quality Guidelines are too vague to be any help.
If you Google the error message you will see other people in the same situation. This doesn’t help, but it makes you feel less alone.
What to do?
Since you receive the rejection in an email.
Reply to the email nicely asking.
“Can you provide more information about why this failed the review and what I have to do to fix it?”
Or words to that effect.
If you are told to resubmit. Then resubmit, expecting to be rejected. Because you will likely go through this process multiple times.
I went through this cycle. With no changes to my extension. 9 times from 26th Feb 2019 until it was accepted into the Chrome Store on the 1st of April.
I suspect it is automatically rejected.
You might get lucky.
If you don’t then keep trying.
- first google the error message
- you’ll see other people in the same situation
- if changes you need to make are not obvious then email support asking for a specific reason
- keep doing this, and submitting and asking, until you get a reason
- eventually, if you persist, you can make it
I’ve created a video showing the steps I took.
Writing a Chrome Extension is pretty easy (getting it in the Chrome Store is much harder!). In this post I describe the steps to release an extension.
I have now released two extensions to the Chrome Store.
Neither went in first try, but both eventually made it after adjusting the description and adding some more screenshots.
I have described the basic process for releasing the extension.
After following this process you may have to refine your entry if it is rejected during the submission process. I’ll describe that process in a later blog.
I have a video showing the full process at the bottom of the post. This text is basically a summary.
You can find the code for both my Chrome Extensions on Github and you’ll see all the images, descriptions and manifest files that I created there if you want to model my final submissions.
Release process summary
Up to date instructions and directions will be on the Chrome Store:
I created an icon in Gimp - 128x128, 48x48, 16x16
Add icons to the manifest
Write a description
Create screenshots for the application of 1280x800 or 640x400
I created a separate google account because the developer email address needs to be public
Create a zip file of the extension, I zipped my code so that the manifest was in the root of the zip i.e. not in a subfolder when unzipped
“Add New Item” from the Chrome Developer Dashboard
paste in all the descriptions, icons and screenshots
Over the submission process I:
- refined the description
- added a few more screenshots
- added a YouTube video showing the plugin in action
I’ve created a video showing this in action.
And you can find the source code on Github.
TLDR; Another month of lots of content with tools, blog posts, patreon and links
And I have newsletter you can sign up for.
Tools & Code
I wrote a couple of Chrome Extensions, and updated my testing practice apps.
- Testing Apps I updated my testing apps so that the REST API and the GUI app have better multi user support.
- Rest Listicator is on Heroku a practice test REST API
- The Pulper is on Heroku The Pulper practice GUI testing app is on Heroku
I’ve been updating my sites and migrated more content over to EvilTester.com
- Migrated my Conference Page Archive
I also updated my services pages to describe in easier format what I do. If you want any consultancy help with testing or development then these pages might help.
- Remote Code Reviews If you want to improve your Test Automation but don’t want onsite consultancy then I can review your code remotely and offer feedback and mentoring.
- Test Automation Improvements - Quick Starts, Next Level, Proof of Concepts
- Bespoke Consultancy
- Agile Coaching
Did you know I have a free guide on “What is Agile Software Testing?”
All my YouTube videos are embedded within blog posts, so I haven’t listed the videos separately.
- How to View URL Query Parameters using Browser Dev Tools
- February 2019 EvilTester.com and Patreon Content Summary
- Are there any programming Katas related to testing?
- What is Software Testing And Why Do We Test Software?
- Which is the best link checking tool?
- Chrome functionality or extensions for responsive web testing?
- Review of Emmet Re-view Chrome extension
- Episode 009 - The Why? Special - The Evil Tester Show
The Evil Tester Show had 2 new episodes released
- What is Software Testing? a discussion of definitions and trying to keep things simple.
- The Why Special how and when to ask questions that get relevant answers, rather than asking “Why?” all the time
Things that caught my eye
I usually post things that catch my eye on Twitter
- Machine Learning - Learning Path a curated ordered list of machine learning resources
- Every Google account has access to a 5 gig cloud VM
- Random Data when Automating
- The Architecture of Open Source Apps Books are available online
- Free hosting options for personal apps and projects not just Heroku
- Smells to refactoring cheat sheet
- Zero to hero security testing course ongoing security testing course with live videos
- Building fast interpreters in Rust
- An overview of K6 performance testing tool
I mentioned a few other things on Twitter but if you scroll through my timeline for February then I’m sure you’ll find them
Some of this is overlap with the blog and YouTube. When I release a YouTube video I also provide it ad-free to Patreons and create a blog post for it. And I discuss my blog posts in more detail with extra thoughts over on Patreon. I also create unique content on Patreon, so there is usual more released on my Patreon site than publicly.
Patreon Posts For March 2019
- BDD, GDA and GAL
- Are we constantly re-inventing the testing we perform?
- New $5 benefit coming soon
- Abstractions Scale When Libraries Fail
- All Models are Useful - revisited
- Newly arrived - Experiencing The Impossible
- New Podcast - The Why? Special
- I, We, You They - the language of influence illustrated in bad and good speeches
- Book Bundle on attitude, courage to speak, negotiation
- Software Testing Checklists?
- Alfred Adler’s Early Recollection technique and courage to speak up
- How to develop a a ‘say what needs to be said’ attitude
- Another Affordable Screen Recording Tool
- Perceptual Positions
- Pulper Test App On Heroku
- Do you really need to write that tool?
- Using Chrome for responsive web testing
- Review of Emmit Re:View Chrome Extension
- That’s not right - reactions to other code and approaches
- Personal Resources - Brief Therapy
- Is Automation the most contentious topic in testing?
- What are you changing? What are you working on?
- Study hard in the most undisciplined, irreverent and original manner possible.
- What is Software Testing, a Simple Explanation
- What is a context free definition of software testing?
- Releasing a Chrome Extension to the Store
- Automating Manual Script Generation
- Code Katas for testing
- Which link checkers do you use?
- February 2019 Content Extracts
- Do what only you can do
I release a PDF which has the full text of all my blog posts and patreon posts as a Patreon benefit to make it easier for Patreon supporters to catchup in batch mode.
Não é uma tarefa tão simples por ADB…Pois tem passos de segurança…Melhor olhar nas classes de desenvolvimento para melhor esclarecimento…