1)If the test team is different than the development team, at what step would yo
ID: 671826 • Letter: 1
Question
1)If the test team is different than the development team, at what step would you involve the test team (test engineer and test manager) in your project activities? How would you do this?
2)If an incident, that looks failure in common sense, observed during a testing activity and the incident is not considered a “failure” per the established “Test Criteria”, what events should take place in the testing procedure?
3)Consider the following program which classifies triangles as one of a scalene, isosceles, right or equilateral triangle and computes its area. Suppose it is initially tested using the first 4 test cases provided in the following table. T5 is added to the test case and program incorrectly computes the area. Debugging reveals an error in Statement 11. It uses expression a*2 instead of a*a. Suppose the fault is corrected and new program must be rerun to verify that it produces the correct output. Recommend a regression test case to reevaluate the program.
Program Code:
S1: read (a, b, c);
S2: class = scalene;
S3: if a=b or b=a
S4: class=isosceles;
S5: if a*a=b*b + c*c
S6: class=right;
S7: if a=b=c
S8 class= equilateral
S9: case class of
S10: right: area=b*c/2
S11: equilateral: area= a*2*sqrt(3)/4;
S12: otherwise: s= (a+b+c)/2;
S13: area= sqrt(s*(s-a)*(s-b)*(s-c));
end;
S14: write (class, area)
Test Cases:
Explanation / Answer
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include the process of executing a program or application with the intent of finding software bugs.
1)Learn to analyze your test results thoroughly
2) Learn to maximize the test coverage every time you test any application.
3) To ensure maximum test coverage break your application under test into smaller functional modules.
4) While writing test cases, write test cases for intended functionality first
5) Think positive.
6) Write your test cases in requirement analysis and design phase itself.
7) Make your test cases available to developers prior to coding.
8 ) If possible identify and group your test cases for regression testing.
9) Applications requiring critical response time should be thoroughly tested for performance.
10) Programmers should not test their own code.
11) Go beyond requirement testing. T
12) While doing regression testing use previous bug graph
13) Note down the new terms, concepts you learn while testing. .
14) Many times testers or developers make changes in code base for application under test.
15) Keep developers away from test environment.
16) It’s a good practice to involve testers right from software requirement and design phase.
17) Testing teams should share best testing practices, experience with other teams in their organization.
18) Increase your conversation with developers to know more about the product.
19) Don’t run out of time to do high priority testing tasks.
20) Write clear, descriptive, unambiguous bug report.
"Reproducing a bug"? : This case occur in 2 scenarios, first , if we found an issue then again we need to confirm whether it's able to reproduce before going to log, second, if the same issue was not able to reproduce by developer then we need to show again as how to reproduce the issue.
So better always maintain the screen shots as proof and provide it along with bug.
If the bug was not reproducable, what is the next step? : If the issue is not able to reproduce in dev environment then try it in testing environment, if it's still not able to reproduce in test environment then try to show the screen shot as issue is there while doing our testing. This will naturally happens when there is conflict in the versions, or if some one upload the new version files with out following the process.
Many times more than one tester is responsible for testing some builds. In this case more than one tester will be having access to common test data and each tester will try to manipulate that common data according to his/her own needs. Best way to keep your valuable input data collection intact is to keep personal copies of the same data. It may be of any format like inputs to be provided to the application, input files such as word file, excel file or other photo files.
Data Mapping: In the software systems, data often travels back and forth from the UI (user interface) to the backend DB and vice versa. So following are the aspects to look for:
To check whether the fields in the UI/Front end forms and mapped consistently with the corresponding DB table Typically this mapping information is defined in the requirements documents.
Whenever a certain action is performed in the front end of an application, a corresponding CRUD (Create, Retrieve, Update and delete) action gets invoked at the back end. A tester will have to check if the right action is invoked and the invoked action in itself is successful or not.
Performance tests require very large data set. Particularly if application fetching or updating data from DB tables then large data volume play important role while testing such application for performance. Sometimes creating data manually will not detect some subtle bugs that may only be caught by actual data created by application under test. If you want real time data, which is impossible to create manually, then ask your manager to make it available from live environment.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.