the problem is not if the BB blocked it or not, the problem is that it was done in a VM , and so the result can't be taken as a real result and can't be used to report it as a flaw , if it was done in real system then the devs can correct the soft properly.
when i watch youtube "Vm-inside" tests , i just watch the UI and resources usage then stop when the malware test begins.
in our case EIS'BB internet was cut but:
- was it the full effect of the malware ? there is 90% chance it is but the 10% left is not acceptable enough to me.
- was it a voluntary effect and consequence of the malware or a side-effect because the malware was running in a VM?
- does this cut will happen in a real system? or the malware will do worse damage but was restrained by the VM so this cut?
- it is reproducible in real system?
You see, too many questions because it was done in a VM; if it was on a real system , i will say nothing then i can produce some legit conclusions but i can't because
it was on a VM.
you (every tester) want be a real tester , go buy a old cheap laptop with WinXP/7 on it and then i will give far more credits than now.
Why do you think medicine/cosmetic firms employ real people as test subjects for their brand new products, it is because a lab simulation NEVER replicates all the events and hazards a real system do.
when i did closed-beta tests, vendors ask me details about a bug/issue i found , when i said it was on a VM, they all ask me to reproduce it on a real system to cross-check it. why do you think they ask ? because they know that VM testing are not 100% accurate and they don't have time and money to waste to correct a VM-inside bug.
rules/guideline about reviews i made: