In the age of social media and Instagram, people are becoming more and more influenced by the lifestyles they see on social media. This gives a rise to aspirations to attain wealth and live a very comfortable if not a luxurious life. Not everyone is blessed with a good amount of wealth, born in an affluent family or have a high income. It is good to work hard towards your goals and achieve success over time but even though most people want to become wealthy, they just don't get it. We all have seen a prince marrying an ordinary woman in fairy tales. In Korean drama, it is very common to see an extremely rich man marrying an ordinary woman or vice versa. Marrying a rich man/woman can be a shortcut for someone to escape poverty and attain the desired level of wealth and financial freedom. During my consultations, several people come up to me with these questions and through this article I want to guide you to find the best approach for your life based on your planetary placemen...
Testing is the process of exercising a system or its components by manual or automated means to verify that it satisfies specified requirements.
1) Debug : Defined as the successful correction of a failure.
2) Demonstrate : Process of showing that major feature work with typical input.
3) Verify : Process of finding as many faults in the application under test (AUT) as possible.
4) Validate : Finding faults in requirements, design and AUT.
5) Prevent : Avoid errors in development of requirements.
To
avoid any misconceptions about testing lets understand the facts which
do not fit in the criteria of testing a system or software.
Testing
is NOT:
a) Process
of showing that the system built is free from errors, bugs, faults or failures.
b) Process
of establishing confidence that the system is robust, light weight, correct and
does what it is supposed to do.
c) Proving
that the build system is able to perform all the functions specified in the
software requirement specifications (SRS) document.
Rather a good tester must be of destructive mentality and should
try to fail the system and check for faults in the system before the customer
or end user does.
This is necessary because spammers, hackers and cyber criminals
try to find errors in systems due to reasons
- Harming the companies name and the trust people place in them
- Benefit the rival company and make customers believe that one is better than the other
- Hack into system to do fraudulent activities.
Check my article on: Positive View of Negative Testing
Software testing can be described with this simple equation
Software
Testing = Software Verification + Software Validation
Verification and validation is already explained but just for
sake of convenience the difference between them is: Verification is checking
whether are the required functions are implemented in the system in order to
call that the software package is complete & Validation is checking how
well the implementation of these functions are done, are they correctly written
and able to perform operations perfectly.
Process of testing runs simultaneously with the Software
Development Life Cycle i.e. we don’t just do testing when the software is
built, testing is done at every phase of development. For example: Unit testing
is done by the developer himself due to the cost factor, and those who write
programs know that while writing codes we simultaneously check them in order to
avoid any tiny possibility of having error in the codes or its implementation.
Activities which are done during the testing process are:
a) Plan
Testing: We check for the programs and
data which can be used to test the current software & modifications to
these programs and data are done accordingly. A log is used to track versions
and keep check on modifications.
b) Identify
& Specify Tests: Parts of programs which are required to be tested and which
makes the crucial part of the application. Then test cases are chosen
accordingly for testing.
c) Execute
Tests: This is done either manually or by automated tools. The application is
exercised and the results obtained are recorded for further analysis.
d) Analyse:
Obtained values are analysed to see if
the results are correct. If they are correct then we finish the tests. If not
then we again go back to specifying the test cases and the re-execute the system
again.
These four are just basic activities which are performed by
almost every coder or programmer (manually most of the times when it is made by
an individual coder). These activities are involved almost everywhere but the
level of testing may change i.e. from unit testing to integration testing to
system testing.
Read about: Levels of Testing.