Why some consider static analysis a testing and some do not?
Preparing myself also to ISTQB certification, I found they call static analysis actually as a static testing, while some engineering book distinct between static analysis and testing, which is the dynamic activity. I tent to think that static analysis is not a testing in the true sense as it does not test, it checks/verifies. But sure I would love to hear opinion of the true experts here.
Thank you
ISO 12207: Verification of integration and Unit test validation
I have received comments from the supervisor reviewing my thesis. He asked two questions I cannot answer right now:
Inspection, code review – is it really testing?
ISTQB, Wikipedia or other sources classify verification acitivities (reviews etc.) as a static testing, yet other do not. If we can say that peer reviews and inspections are actually a kind of a testing, then a lot of standards do not make sense (consider e.g. ISO which say that validation is done by testing, while verification by checking of work products) – it should at least say dynamic testing for validation, shouldn’t it?
I am completing master thesis dealing with QA and I must admit that I have never seen worse and more ambiguous and contradicting literature than in this field :/
Do you think (and if so, why) that static testing is a good and justifiable term or should we stick to testing and static checks/analysis?
Quality Assurance activities [duplicate]
Possible Duplicate:
Verification of requirements question
Is asking for control totals on a file an outdated means of verifying a file?
I’m in a new position where I need to process a flat files on a regular basis. The last time I did this was 5 or 6 years ago but as part of the file layout I received control totals. It gave me simplistic information on the file like the total number of records as well as sums of the important fields. This helped me during testing then also during production to verify the file arrived and has correct information.
Creating an account to receive sensitive information on a mobile device
I am developing an Android application for my final year project which allows the holder of a mobile device to receive a text notification containing potentially sensitive information from a server.
How to authenticate an archive
Background:
I have a updator feature in my program which will downloads updates to a directory specified be the user. Then user can install these updates whenever he/she wants by just opening them. These updates are nothing but a compressed archive file which is associated to be opened by my app.
Verification of requirements in a closed system
I’m on my first real software project following the whole SDLC and am a bit confused. We have a requirement that states something like “The battery will be monitored each second” which needs to be verified. This is something that can’t really be checked in the system since it happens “inside”, i.e. there’s no output that would show that the battery was checked each second. It is my understanding that at this phase the verification is done on a closed system, so you can’t just use a debugger to verify something like this.
SMS verification in web application [closed]
Closed 11 years ago.
SMS verification in web application [closed]
Closed 11 years ago.