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
https://talkingabouttesting.com/2019/04/04/bate-papo-sobre-refatoracao-com-gabriel-oliveira/
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.
Multiple times.
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.
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.
I’ve created a video showing the steps I took.
If you are interested in writing a Chrome Extension then check out all blog posts in this category Chrome Extension and see the videos in this Chrome Extension Playlist
https://eviltester.com/blog/eviltester/2019/04/03-chrome-extension-rejection/
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.
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:
I’ve created a video showing this in action.
And you can find the source code on Github.
https://eviltester.com/blog/eviltester/2019/04/02-how-to-release-a-chrome-extension/
TLDR; Another month of lots of content with tools, blog posts, patreon and links
If you want to keep up to date on a more regular basis you can follow me on - Linkedin, Twitter, Instagram, Facebook, Youtube
And I have newsletter you can sign up for.
I wrote a couple of Chrome Extensions, and updated my testing practice apps.
I’ve been updating my sites and migrated more content over to EvilTester.com
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.
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.
The Evil Tester Show had 2 new episodes released
I usually post things that catch my eye on Twitter
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.
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.
https://eviltester.com/blog/eviltester/summaries/2019-04-01-march-2019-summary/
“Why?” is an incredibly popular question.
I think it has problems. I try to avoid it when I’m consulting.
In this show we will examine “Why?” and under what circumstances I do use it.
“Why?” is almost a default question because it can take the place of every other question. It is easy to ask. We don’t even need to know what answer we want. It’s also a very ambiguous question, and when we ask why there is a risk that people try to read into our motivation, and that people might take offence.
When I’m working with clients and I come in for a week, I have a short period of time to build a model of the system of development, the interactions, the reasons, the issues, etc.
I could ask Why? a lot.
I don’t usually do that because:
If I want to long consultancy engagement that build dependency on me as a consultant then Why? could be a great question because I can chain whys and get a really long discussion and lost of vague concepts to follow up.
When I consult I want actionable insights, next steps, obvious alternatives, evidence.
If you want software testing or development consultancy then check out EvilTester.com/consultancy
“Why is the sky blue?” …answer… “Why?”
As children it is almost a default question, it is easy to ask, we get answers, and its fun to see people get frustrated when we keep asking it.
In IT, Management, Engineering we often taught that it is a good question - the Five Whys Technique.
It’s a default. The reason I say that is because I’ve been working hard on my own problem solving processes to avoid it being a default but when I’m not keeping a tight rein on my thinking, it pops up.
But when we ask “Why?” we don’t know what question people will actually answer. It is quite a vague question.
Anytime we ask why, we do no know how people will interpret it. Will they interpret it as a What? How? Where? When? Who?
Or will the interpret it as:
This might be evidence supported or belief supported.
Historical context:
Example:
This is very focused on a specific problem. With evidence based answers at each step.
In software or consultancy…
Difference:
Five whys could easily be rephrased as the “What caused this?” chain to five levels of direct relationships.
“Five Whys” might be targeting people’s beliefs.
“What do we believe is the reason for writing test scripts in this process?”
Is there is risk in chaining beliefs?
Sometimes beliefs aren’t based on evidence.
Humans are very good at having and maintaining beliefs despite evidence.
People are also very good at defending their beliefs.
If we keep asking why then people might go into defensive mode which impacts our ability to work with them.
And when I’m consulting I can’t afford the time that that resistance creates.
Easier to avoid it in the first place.
Why is a very good question for working with people’s beliefs. And if you are trying to effect change in an organisation you will probably have to clarify those beliefs and work with them on an individual basis.
People often avoid saying “I don’t know”
If we ask “Why” and someone doesn’t know. We risk asking them to “make something up” to avoid saying they don’t know.
That then becomes a belief.
And we put them in the position where they have to continue to justify that statement that they just made up.
Without a proper context to questions people may read motivations into the question.
“Why?” can trigger a lot of negative motivation.
“How”“, “When?” etc. are more neutral and trigger less resistance.
But do you know why you are asking?
We have to have more conscious direction over our questions if we are problem solving or building specific models.
If we are building a model from nothing, and all information that comes back is valid then it doesn’t really matter what we receive in response then it might be a valid default.
But at some point we have to decide what information we want to receive in the answer. And if we create questions that target that answer they probably won’t be “Why?” questions.
Usually about the person your asking, rather than the thing you are asking about.
But try it for yourself
When you ask a “Why?” question - think:
If this interests you then try and avoid “Why?” ask “What”, “How”, “Who”, “when”, “where” type questions instead.
and I’ll leave you with a couple of quotes.
This is from Fritz Perls Book The Gestalt Approach on page 77
“The why questions produce only pat answers, defensiveness, rationalizations, excuses and the delusion that an event can be explained by a single cause. They why does not discriminate purpose, origin, or background. Under the mask of inquiry it has contributed perhaps more to human confusion than any other single word”
And… he goes on to suggest that if we pursue inquiry with a why that we
“join the group of worrying grandmothers who attack their prey with such pointless questions as ‘Why did you catch that cold?’ and ‘why have you been so naughty?’”
If you want a quote for test consultancy contact me via eviltester.com/consultancy
And if you found value in this or any of my podcasts, do let people know or like this on itunes or youtube or wherever you found it.
Proactively tell people about good stuff rather than have them ask you “why are you listening to that?”
Mais um post da série de qualidade de código em teste de software Se você está chegando neste post agora e ainda não leu os conteúdos anteriores, recomendo começar por eles. Seguem os links: Escreva pequenas unidades de código Escreva simples unidades de código Escreva código uma só vez Mantenha as interfaces da unidade pequenas … Continue lendo Separe responsabilidades em módulos
https://talkingabouttesting.com/2019/03/18/separe-responsabilidades-em-modulos/
TLDR; Emmet Re:view is a useful Chrome extension for responsive layout testing
During my search for responsive testing tools I found Emmet Re:view, and reviewed it.
Emmet Re:View matches some of my requirements for responsive testing but mainly it offers a potential time saving time of showing many different sizes at the same time.
I wrote a crude tool many moons ago for responsive layout testing - it uses iframes and is a bit clunky.
Emmet Re:view runs as a chrome extension and can show a page as multiple sizes at the same time.
You can configure the set of renderings used.
And the page is scrolled at the same rate so you can see much of the same content in each view at the same time.
Unfortunately I couldn’t get the media query breakpoints view to work, but the multiple rendering view is useful enough to consider using this plugin for.
If you found this useful then you might be interested in my Online Technical Web Testing 101 course.
Learn More About Technical Web Testing
https://eviltester.com/blog/eviltester/2019-03-15-emmit-review-responsive-layout-testing-itool/
TLDR; Chrome has built in functionality for visualising media queries
Are there any good tools for helping me with responsive testing so I can see what media queries are used in a page and then resizing to that resolution for testing?
At UKStar I was speaking to Angie Jones and the topic of responsive testing came up, being able to see your site at multiple resolutions for different devices would be a very useful tool to have.
Also, when I think about this, I want to have very specific application view i.e. what resolutions have I actually coded for, to make sure I trigger the different combinations - not just the general device rendering.
My initial thought was that I should look for a Chrome extension. And indeed that is what I did. The rest of the blog post covers that investigation.
After having performed this investigation, found an extension, fixed a bug in the extension, I realised…
“I wonder if the browser does this already?”
I should have started here.
Given my existing tool set, can they meet my needs?
In Chrome.
This will show the responsive view
Click the “Show Media Queries” menu:
This will show a rendering of the Media Queries on the site
This shows me the media queries that are active on the page and I can:
I would have had a more productive morning if I had performed this step first, but I didn’t, I did it after I looked for Chrome Extensions, Evaluated Extensions, Fixed a Chrome Extension… as you will see.
Extensions are generally released to Chrome Store
But I’m also aware (since I have tried to submit two extensions to the store, but only one has been accepted) that there are other extensions available as source that might be better, but I won’t know about.
But I’ll try the search and the “Related” suggestions from the store first.
A few products came back and after reviewing the descriptions I reduced the list to:
Responsive Inspector looked like it matched my requirements pretty well.
Emmet Re:View matches some of my requirements but looked like it might offer a potential time saving time of showing all the different sizes at the same time.
SeeResponsive looked like a light weight version that might support fast switching.
I revisited each of the extension pages to check the “related” list at the bottom of each extension page to see if that helped me find additional tools.
There were a few tools that seemed interesting but because they used ‘hard coded’ sizes they didn’t quite match my need of targeted risk assessment for the current system. They were more suited for generic web development support and I could achieve much the same result with the in built chrome responsive view and its predefined device list.
Interestingly the ‘related’ view found “Responsive Inspector Reloaded” which is a forked version of Responsive Inspector which hasn’t been updated since 2013 and the comments on Responsive Inspector Reloaded suggest that Responsive Inspector doesn’t work on modern browsers.
I tried Responsive Inspector Reloaded and it didn’t work as I expected, perhaps this doesn’t work on ‘modern browsers’ since it hasn’t been updated since 2017.
I tried Responsive Inspector and as the comments on the Reloaded version suggested, it didn’t work on my up to date browsers, failed with the same user experience as Reloaded.
I tried SeeResponsive, and that gave an error loading the CSS on my page. I tried it on another page and it functioned. It didn’t give the user experience I was expecting so it isn’t suitable for my needs.
I tried Emmet Re:View and the Device Wall is interesting but not as configurable as I expected. And the Breakpoints view doesn’t show me the breakpoints in the page. I might still use this for exploratory testing because it shows me a range of sizes and I can interact with them at the same time.
Danger: if you know how to code you might fall into the trap of trying to write something that already exists without fully exploring all current options. I almost did.
I had a quick look at the Responsive Inspector Reloaded code.
Now that I’ve built Chrome Extensions I have some familiarity with looking at the code.
Rather than ‘try to make it work. I decided to pull out the essence and see if I could get it to work. The main code was a single method in the content.js called getMedia
I found an exception was thrown in the code.
A web search later and I found a suggested try catch block fix.
This is because various security measures have been added to Chrome since the extension was written and now, when a trying to access details of a stylesheet from a different domain, an exception is thrown.
Wrapped try catch and the code worked.
I downloaded the source from the original github repo to run as an unpacked extension.
I added the Try Catch in the getMedia method in the extension and it worked.
Well, almost. The screenshot functionality didn’t work but the at least the pop up menu now showed the media queries.
Someone had raised an issue on the main project for this defect:
https://github.com/MistaTwista/Responsive-Inspector-Reloaded/issues/2
So I added a comment with my fix.
The next step would really be to add a pull request with the fix.
But I’m not going to do that, because… while I think the extension is useful, I will probably just use the built in browser functionality.
If I was going to fix it I would start here to learn about forking, fixing and pull requests
If you found this useful then you might be interested in my Online Technical Web Testing 101 course.
Learn More About Technical Web Testing
https://eviltester.com/blog/eviltester/2019-03-13-responsive-layout-testing-in-chrome/
Hello guys, today I am going to post a workaround that I am doing to get test reports from a kubernetes pod that has terminated. If you run your tests in a kubernetes pod, you must know by now that you can’t copy your files containing your test reports from a terminated pod. Many people … Continue reading How to get your test reports from a pod – Kubernetes →
https://azevedorafaela.com/2019/03/10/how-to-get-your-test-reports-from-a-pod-kubernetes/
I was asked “Which is the best link checking tool?”. And I don’t know. But I do know that I use Total Validator Pro and a Chrome Plugin called Check My Links.
It might be useful to know if there is actually a ‘best’ tool in a particular category.
But I find that if you look for “The Best” then you end up continually hunting and are subconsciously unsatisfied with the tools you use.
I covered this topic in my podcast episode The Evil Tester Show - Tools Special.
I use the best I’ve found. And they meet my needs. So I stopped looking.
And I use two:
I’ve written about Total Validator Pro before
It spiders my site:
I run it periodically and it helps general health of the site, it also gives me a back log of work.
Check My Links from pagemodified.com is a Chrome Extension.
It runs against a specific page and visually shows me the state of the links.
I use it after I’ve made a change or am testing a specific page. It runs quickly and I can see any issues visually.
It was the second Chrome extension I tried. It worked for me. I kept using it.
Rather than looking for “The Best”, look for a combination of tools that support your workflow and requirements.
I prefer cross platform tools where possible so I don’t have to keep too many different names in my memory.
You can see both tools in action in this YouTube video:
If you found this useful then you might be interested in my Online Technical Web Testing 101 course.
Learn More About Technical Web Testing
https://eviltester.com/blog/eviltester/2019-03-04-which-is-best-link-checker/