Author Topic: What is system testing?  (Read 2944 times)

Offline Vijay

  • Administrator
  • Sr. Member
  • *****
  • Posts: 100
  • Karma: +1/-0
    • View Profile
    • Software Testing Help
What is system testing?
« on: July 04, 2010, 03:27:11 AM »
[This is sample question to show you what type of questions can be asked under this topic]

What is system testing?
Passion for Testing, Passion for Quality!
http://softwaretestinghelp.com

Offline Vijay

  • Administrator
  • Sr. Member
  • *****
  • Posts: 100
  • Karma: +1/-0
    • View Profile
    • Software Testing Help
Re: What is system testing?
« Reply #1 on: July 04, 2010, 03:27:28 AM »
System testing:
The process of testing an integrated system to verify that it meets specified requirements.
Passion for Testing, Passion for Quality!
http://softwaretestinghelp.com

advertisement

Offline Mayasen

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 189
  • Karma: +0/-0
  • Mayasen
    • View Profile
Re: What is system testing?
« Reply #2 on: August 29, 2010, 11:31:10 PM »
Testing the complete product i.e. once the developement get over then the product will go for complete testing. Before System testing, the product should cross the Unit and Integration testing.

Once the system test is completed, the product will be released as "Beta" version for UAT and Usability Testing. :)
« Last Edit: August 29, 2010, 11:57:21 PM by Mayasen »
--
Mayasen

Offline nilesh

  • Full Member
  • ***
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Re: What is system testing?
« Reply #3 on: August 31, 2010, 08:24:29 AM »
System testing is process where we check behaviour of the system.
Load, Stress, Performance are type of system testing.
It is last stage before lounching software system.
as business model in SDLC we set, we check that we meet it or not with system testing in STLC

Offline swtmentor

  • Jr. Member
  • **
  • Posts: 3
  • Karma: +0/-0
    • View Profile
    • Software Testing Mentor
Re: What is system testing?
« Reply #4 on: December 31, 2010, 05:30:33 AM »
System Testing tests the behavior of the whole software as defined in software requirements specification, its main focus is to verify that the customer requirements are fulfilled. It is done after integration testing.

Some of the testing types which needs to be covered in system testing are as follows:

1. Sanity Testing
2. Functional Testing
3. Usability Testing
4. Stress Testing
5. Performance Testing
6. Regression Testing
7. Maintenance Testing
8. Security Testing

Offline dheerajs

  • Full Member
  • ***
  • Posts: 33
  • Karma: +1/-0
    • View Profile
Re: What is system testing?
« Reply #5 on: March 01, 2012, 10:13:10 PM »
Hi Vijay

Software testing has four level:
1. Unit testing level
2. Integration testing level
3. System testing level
4. Acceptance testing

In system testing we test the whole application with the specified requirement.Generally the System testing is done before acceptance testing, but in some cases it can also be done after acceptance testing. here we check all the functionality of application, at the same time we also check the non functionality like reliability, time to load a page, security, portability etc.....

Offline Mayasen

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 189
  • Karma: +0/-0
  • Mayasen
    • View Profile
Re: What is system testing?
« Reply #6 on: March 16, 2012, 01:40:56 AM »
//System testing is done before acceptance testing, but in some cases it can also be done after acceptance testing. //

Hi dheeraj,
I am not clear about your comment, could you please explain in which case we will perform System Test after the Acceptance Test?
--
Mayasen

Offline dheerajs

  • Full Member
  • ***
  • Posts: 33
  • Karma: +1/-0
    • View Profile
Re: What is system testing?
« Reply #7 on: April 05, 2012, 11:02:24 PM »
Hi Mayasen

Sorry for late response

As per my knowledge, Acceptance testing is done to build confidence in the system, so that the product can be accepted by user.At this level our motive is to check whether we can release the product  and not on finding new bug. In other word we can say that acceptance testing is done to satisfy the stakeholder, this stakeholder can be a group of 2 person or a crores of person including user etc...

Some example where acceptance testing is done at different level of testing.

1.)  A Commercial Off The Shelf (COTS) software product may be acceptance tested when it is installed or integrated.
2.)  Acceptance testing of the usability of a component may be done during component testing.
3.) Acceptance testing of a new functional enhancement may come before system testing.
4.) A large-scale system integration test may come after the acceptance of a system.

Note:
Source : Foundations of software testing By Rex Black, D Graham etc..


Now think of a practical scenario,

Gmail is a web application, It had been installed on some box(server or system) first then application would have been tested exhaustively, when the application seems working fine i.e. system testing and acceptance testing is done it is released in market.
At the time of installation if the application is not installed properly will the developer or tester be able to work on that application? Certainly not. So successful installation of application is required and we can say that installation is successful if it go through acceptance testing to satisfy the stakeholder at that time i.e. developer, tester, the owner of application.

This is my thinking, my view may be wrong, may be right. I am trying to learn more about it.If you disagree mail me at:
dheeraj.silicon@gmail.com


With Regards
Dheeraj