8 votes

Is it a good idea for a Developer to review a tester's code

It's an okay idea with some guidelines. QA code is software. And software engineering principles should still apply. Since none of the developers know protractor, they should be trained. They may ...
user avatar
  • 589
7 votes
Accepted

How to inspect elements on pages with 'loading' spinners?

Chrome provides an inbuilt function for this: Dev Console (F12) Switch to the Sources tab Do action in browser to get to the state you want to inspect Press F8 Chrome will pause the browser and ...
user avatar
  • 524
4 votes
Accepted

Strategies for discovering undocumented API

You can use tools like owasp zap to find all the API calls. It spiders through most of the endpoints in search of security vulnerabilities. https://www.owasp.org/index.php/...
user avatar
  • 10.8k
3 votes

Assertion on static value or calculated one

I would consider the whole idea of verifying such logic from the UI perspective as a bad practice. See info on test pyramid. If you need to test the calculation logic of your service - you can do ...
user avatar
3 votes

Strategies for discovering undocumented API

If you have no endpoint documentation then the things are really bad. I would use the following aproach: examine known clients which use the api extract all possible invokations which the client can ...
user avatar
  • 399
3 votes

Is it a good idea for a Developer to review a tester's code

Why do you view it as 'Developer' reviewing 'tester's code? A team member is reviewing another team member's code is perfectly fine as long as vice-versa is also true and accepted equally. ...
user avatar
2 votes

Do you test methods that return queries from the database?

You can't really test the output of a query with unit testing. There are two broad options: You could write unit tests that validate the expected value of the query string for given inputs. However, ...
user avatar
2 votes

How often should system tests be run?

It all comes down to finding a balance point between cost of achieving quality and quality. Perhaps you can start by calculating average time it takes for system tests to find a bug? E.g. If it takes ...
user avatar
  • 9,720
2 votes

Best guidelines for bug reporting?

Checklist for publishing a good bug report: Look for duplicates Check for accuracy in all elements of the bug report Roleplay as a different recipient (for example, a Test Manager) and ask if the bug ...
user avatar
  • 326
2 votes

How to inspect elements on pages with 'loading' spinners?

Pausing the application as Klynt suggested should work in most situations to find elements that appear and disappear quickly. Still, do not under estimate the power of contacting the developers and ...
user avatar
2 votes

Automate the stable build only

It is actually about Automation best practice There are good practices in context, but there are no best practices. I have the understanding that Automation Scripts need to be built on a stable ...
user avatar
  • 9,949
2 votes

Automate the stable build only

I don't know if an authoritative answer can be provided, but I think simple logic should suffice: your primary use of automation is regression developing automation scripts takes (a lot) more time ...
user avatar
  • 4,079
1 vote

Whats the best approach to select elements for automated testing?

The best practices are a good guide but implementation always "depends" Generally you want to use ID and data- attributes. It's that simple. The complications arise from real world ...
user avatar
1 vote

Strategies for discovering undocumented API

My approach would be to examine the network traffic. If the application operates over HTTP/HTTPS, the easiest way to do this is to use a tool called mitmproxy as a proxy that sits between the client ...
user avatar
1 vote

Strategies for discovering undocumented API

My experience is that even if there is some documentation, it's quite often rather vague and incomplete. So, you should never completely rely on just documentation even if it's presented to you as ...
user avatar
  • 4,338
1 vote

Is there a better way to code-review JMeter test-plans?

Unfortunately JMeter .jmx files are basically XML and in case of large test plans it might be not very easy to view the diff. You can consider using i.e. Ruby-JMeter which is a Ruby DSL wrapper ...
user avatar
  • 12.6k
1 vote

How to inspect elements on pages with 'loading' spinners?

To me the answers about an immediate technical solution to the problem are a simple fix to the symptoms and not for the source. You haven't mentioned testers having limited access to developers or ...
user avatar
  • 6,945
1 vote

How to inspect elements on pages with 'loading' spinners?

Solutions 1. Use "Element is not clickable at point (x, y). Other element would receive the click..." I think most Selenium users have seen something similar to this: org.openqa.selenium....
user avatar
  • 4,079
1 vote

What are important rules of static analysis to use in our automated scripts?

How about an code review from an experienced senior developer, so that you can focus more on practical tips. Experience is incomparable to any tool at least in the current state of the tools. Having ...
user avatar
1 vote

What are important rules of static analysis to use in our automated scripts?

Try out https://docs.sonarqube.org/display/SONAR/Analyzing+Source+Code Other possible ways If coding guidelines and standard followed. Duplicate code. Coding guidelines followed. Design principle ...
user avatar
1 vote

Is it a good idea for a Developer to review a tester's code

I don't agree with this.Test code should not be reviewed by development team as it may get biased. You can groom people from test org. to be proficient and there are enough materials and best ...
user avatar
1 vote

Best guidelines for bug reporting?

when you said Guidelines I immediately thought about what we have for a Template of necessary information Environment URL Parameters Issue/Defect/Bug (whatever you call it) Description if more ...
user avatar
  • 567
1 vote

Best guidelines for bug reporting?

Specs: Software Version, Database Version etc. Description: The behavior expected vs the behavior met. Reproduction: The exact input needed to run into the bug. Routing: The "adress" where this ...
user avatar
1 vote

Best guidelines for bug reporting?

BBST Bug advocacy course uses RIMGEA acronym that helps you to write and sell effective bug report. I explained RIMGEA acronym in this blog series. R stands for Replicate - you need to be able to ...
user avatar
1 vote

Best guidelines for bug reporting?

I think my previous answer also applies here. In my opinion, the best possible bug report (assuming that the person that sends the error report does not know the causes of the observed failure) is a ...
user avatar

Only top scored, non community-wiki answers of a minimum length are eligible