• 1 Post
  • 41 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle












  • https://gs.statcounter.com/faq#page-views-uniques

    We measure internet usage trends. To accurately measure usage, we have to base our stats on page views (and not unique visitors). Let’s look at an example:

    Person X uses two browsers. On a particular day, they load one page in Browser A. They load 500 pages in Browser B.

    If we based our stats on unique visitors then usage of Browser A and B would both be recorded as 50%. This is obviously incorrect. This does not fairly represent the usage of the browsers given that Browser B was used 500 times more than browser A.

    Using page views as the basis of our stats means that Browser A will be recorded at less than 1% in our stats whereas Browser B will be recorded at over 99%. In our view, this gives a more accurate representation of actual browser usage.





  • That sounds strange. I cannot comment on your particular case without seeing the test artifacts.

    Generally speaking, there is nothing wrong with tests that ensure bad input doesn’t break the system, as this can easily lead to incorrect system states, damage to the environment, loss of data, money, reputation, and even lives - although most systems are not critical enough to threaten lives.

    You wouldn’t need QAs if you only needed to validate that the product meets the requirements. In a typical company, many people are involved in that process. This includes the developer who wrote the code, the developer who reviewed it, and the people who conduct acceptance testing, among others. If your developers produce code that doesn’t meet the requirements, you’re in trouble.

    I’m not saying that QA shouldn’t validate whether the system meets the requirements, but you don’t want them to do just that.