Monthly Archives: December 2016

Ultra Code 2016-12-16 15:25:00

Ankit Gupta
Week – 11

What is the good test case

Test case help us to discover the information. different types of tests cases are more effective for different classes of information. Tests case can be good in a variety of way.  No test case will be good in all of them. People tend to create test cases according to certain testing styles, such as domain testing or risk-based testing. Good domain tests are different from good risk-based tests. In my view, a test case is a question that you ask of the program. The point of running the test is to gain information, for example whether the program will pass or fail the test. It may or may not be specified in great procedural detail, as long as it is clear what is the idea of the test and how to apply that idea to some specific aspect feature, for example of the product. If the documentation is an essential aspect of a test case, in your vocabulary, please substitute the term “test idea” for “test case” in everything that follows. Find safe scenarios for use of the product find ways to get it to work, in spite of the bugs. Sometimes, all that you’re looking for is one way to do a task that will consistently work–one set of instructions that someone else can follow that will reliably deliver the benefit they are supposed to lead to. 

From the blog Ultra Code by Alex Gupta and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 14:52:00

Ankit Gupta
Week – 10

Functional testing focus on what the system does, rather than how does it work.  Non functional testing is focus on what systen does and how it does. Both function are focus on behavior.  white box tests function system based on how does the system work from inside.
functional test bases on funtional requirements. Funtional tests are different than integration tests. A functional integration test will focus on the functionality of a collection of interfacing modules, usually in terms of the partial or complete user workflows, use cases, operations, or features these modules provide.A functional system test will focus on the functionality of the application as a whole, complete user workflows, use cases, operations, and features. A functional system integration test will focus on end-to-end functionality that spans the entire set of integrated systems.

From the blog Ultra Code by Alex Gupta and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 02:12:00

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

  • Wait for all modules to be developed.
  • Time consuming
  • Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

  • Used in top down approach
  • top most modules is tested first 
  • dummy program of lower level components

Driver

  • Used in bottom up approach
  • lowest modules are tested first
  • dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 02:12:00

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

  • Wait for all modules to be developed.
  • Time consuming
  • Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

  • Used in top down approach
  • top most modules is tested first 
  • dummy program of lower level components

Driver

  • Used in bottom up approach
  • lowest modules are tested first
  • dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 02:12:00

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

  • Wait for all modules to be developed.
  • Time consuming
  • Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

  • Used in top down approach
  • top most modules is tested first 
  • dummy program of lower level components

Driver

  • Used in bottom up approach
  • lowest modules are tested first
  • dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 02:12:00

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

  • Wait for all modules to be developed.
  • Time consuming
  • Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

  • Used in top down approach
  • top most modules is tested first 
  • dummy program of lower level components

Driver

  • Used in bottom up approach
  • lowest modules are tested first
  • dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 02:12:00

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

  • Wait for all modules to be developed.
  • Time consuming
  • Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

  • Used in top down approach
  • top most modules is tested first 
  • dummy program of lower level components

Driver

  • Used in bottom up approach
  • lowest modules are tested first
  • dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 02:12:00

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

  • Wait for all modules to be developed.
  • Time consuming
  • Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

  • Used in top down approach
  • top most modules is tested first 
  • dummy program of lower level components

Driver

  • Used in bottom up approach
  • lowest modules are tested first
  • dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 02:12:00

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

  • Wait for all modules to be developed.
  • Time consuming
  • Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

  • Used in top down approach
  • top most modules is tested first 
  • dummy program of lower level components

Driver

  • Used in bottom up approach
  • lowest modules are tested first
  • dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.

Ultra Code 2016-12-16 02:12:00

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

  • Wait for all modules to be developed.
  • Time consuming
  • Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich – which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

  • Used in top down approach
  • top most modules is tested first 
  • dummy program of lower level components

Driver

  • Used in bottom up approach
  • lowest modules are tested first
  • dummy program for higher level component

From the blog Ultra Code by Anonymous and used with permission of the author. All other rights reserved by the author.