upnorthsox
Veteran
There's some nice formatting though.It's almost like the github data is incomplete, fragmentary, filled with errors, lacking context and not actually proof of anything.
There's some nice formatting though.It's almost like the github data is incomplete, fragmentary, filled with errors, lacking context and not actually proof of anything.
Informative of what?
What have the Insiders told us about PS5 that was actually informative and confirmed?
That said, unlike the github data, the insiders are relaying information they've explicitly been told is about the expected final hardware configuration.
Some are telling us the target specs (like the first journalists or Klee) because 1/ those can change 2/ they wouldn't give the exact same numbers to devs for various reasons. But mostly they shouldn't give the exact values because they know some of those numbers will be passed to Microsoft somehow. Dev wouldn' t need the precise target specs anyway. An approximation should be enough.I can accept that, but at the same time it's deflating to see paragraphs from various insiders only to have all the words parsed down to no information at all or merely a "things change". Why are they all Mercutio?
I can accept that, but at the same time it's deflating to see paragraphs from various insiders only to have all the words parsed down to no information at all or merely a "things change". Why are they all Mercutio?
Pretty sure an insider said PS5 had VRS despite people vehemently claiming otherwise because of GitHub.And yet it's still more informative than the Insiders.
Data doesn't lie man. It's either there or not there. It's either accurate data or not accurate. Data has no judgement, but it's on us to make sure things add up properly. People's interpretation of data can be wholly off base. And we see that happen _all the time_.Pretty sure an insider said PS5 had VRS despite people vehemently claiming otherwise because of GitHub.
The purpose of the threads and all of our discussion is to break and test theories. I get people get super annoyed by it. But all of our science superstars had to talk through their ideas with peers as well.If that github leak data inplied 13TF, would any try to poke holes, try to atleast?
If it was implying that it's running it by running at 2.0Ghz, yes absolutely.If that github leak data inplied 13TF, would any try to poke holes, try to atleast?
Data doesn’t lie, except for when the intern enters things wrong and puts stuff in the wrong folders, like in this exact case.Data doesn't lie man. It's either there or not there. It's either accurate data or not accurate. Data has no judgement, but it's on us to make sure things add up properly. People's interpretation of data can be wholly off base. And we see that happen _all the time_.
I explicitly wrote way back when this information is released that it is not all the data, and the tests that were shown were unlikely to be everything. Without context of what they were testing one could not make that assupmtion except to troll people's insecurities.
I talked about it here Jan 10
https://forum.beyond3d.com/posts/2097126/
Regression Test Selection
Selecting test cases for regression testing
- Instead of re-executing the entire test suite, it is better to select part of the test suite to be run
- Test cases selected can be categorized as 1) Reusable Test Cases 2) Obsolete Test Cases.
- Re-usable Test cases can be used in succeeding regression cycles.
- Obsolete Test Cases can't be used in succeeding cycles.
It was found from industry data that a good number of the defects reported by customers were due to last minute bug fixes creating side effects and hence selecting the Test Case for regression testing is an art and not that easy. Effective Regression Tests can be done by selecting the following test cases -
I think anyone passing the narrative those specific tests for Github was absolutely everything is wrong. But to say Github data is false is also wrong. It's the people who made incorrect analysis of it who were wrong.
- Test cases which have frequent defects
- Functionalities which are more visible to the users
- Test cases which verify core features of the product
- Test cases of Functionalities which has undergone more and recent changes
- All Integration Test Cases
- All Complex Test Cases
- Boundary value test cases
- A sample of Successful test cases
- A sample of Failure test cases
If that github leak data inplied 13TF, would any try to poke holes, try to atleast?
If there were a bunch of directly contradictory reports from credible "insiders"? Yes, of course.
credible "insiders"
yea but you guys figured that out which means the process of debate and checking evidence works! you asked questions and realized where there are errors. You didn't take things at purely face value.Data doesn’t lie, except for when the intern enters things wrong and puts stuff in the wrong folders, like in this exact case.
Seemingly, there's no such thing this time around, seeing how much things change.
I consider Jason from Kotaku and Reiner from Game Informer credible. Not random Gaffer of the week cosplaying.