Hi Friends, Hope you are doing great! If you have the perfect match for the below requirement please forward me your consultants most updated word Formatted resume along with the best rate and contact information.
*****For Immediate feedback please forward your resume to [email protected] ***** *Job Title:* Applications QA tester *Location:* NYC *Duration:* 2+ Months * * *Position Description:* Under the general direction of the Director of Student Information Systems, with latitude for independent initiative and judgment is responsible for unit, integration and stress testing of applications developed in Microsoft .NET environment. DUTIES AND RESPONSIBILITIES: *Basic unit and integration testing:* · Analyze requirements and system documentation to develop comprehensive test plans and test strategy. · Develop and maintain comprehensive test plans, test scripts and test cases. · Collaborate in preparation of the test data. · Develop and execute complex SQL queries to analyze the data requirements and backend test results of the data-driven web applications. · Execute testing for functional, end-to-end, and regression testing for various system applications. · Validate test results to ensure requirements are met for user sign-off. · Conduct test script walkthroughs for user review. · Identify, log, and track software defects to resolution. · Provide test defect status reports and statistics to application development team. · Prepare test summary reports at the conclusion of a system test *Stress and Scalability testing:* 1. Working with the application business owners, the team should identify the common usage scenarios for the application and establish some estimate as to how often and by how many people each scenario will be exercised. The team should also identify whether the usage scenarios are seasonal or fluctuate in spikes over time. 2. Each of the primary scenarios should be scripted/coded as load-generation modules. This should be done using a commercial tool such as Visual Studio Team Test, Loadrunner, or SilkPerformer. 3. Around the time of the first beta or release-candidate, the team should establish baseline scalability metrics for the application in the stress-testing environment. *Note: this is not necessarily intended to measure the supportable usage load in the Production environment. The purpose is to establish a point of comparison to evaluate whether future builds have a positive or negative effect on performance/scalability. 4. As appropriate, the results of the baseline and subsequent testing should be analyzed and used to evaluate whether any corrective action should be taken with regard to scalability/performance. This can include, but is not limited to: · Negotiate with business owners to remove features which cause bottlenecks. This should be a cost/benefit discussion. e.g. (Unlimited Ad-Hoc Queries against large data stores) · Acquire additional/more powerful hardware. · Re-design/Optimization of portions of the code which cause bottlenecks. * * *Testing other areas of coding:* All portions or components of the application which involve the use of custom source code should include the following features and processes: 1. All source code will be maintained in the source code repository. Currently, this is either Visual SourceSafe or Team Foundation Server. 2. Each deployed build should be labeled in the repository according to a documented convention. For example: [ApplicationName]-[ModuleName]-[Release|ReleaseCandidate|Debug|Beta|Alpha]-[Year-Month-Day]-[ReleaseNumber] 3. Each deployed build should include a list of: (This should NOT become a feature spec. A simple list is suitable) - New features. - Deprecated features. - Fixed Bugs (If possible include a unique id from a bug-tracking system). - Known Issues and work-arounds. - Unit test results. 4. An exception logging framework. 5. As bugs are assigned and fixed, the bug-tracking system should be updated to reflect the change in status. 6. A unit-testing framework such as NUnit or VSTT unit test projects. Each module will have at least one associated unit test component. *There will be some components for which unit testing is not really appropriate, but these will be the exception rather than the norm. In addition: As bugs are identified by the QA team, the development team should evaluate the possibility of including a unit test which would reveal the same defect automatically. 7. Unit tests should be completed against the integrated build/release, rather than individual components in isolation. Isolation testing is also encouraged and often useful. However, unit tests should be performed on the integrated build to reveal any integration/environment issues. 8. Complex portions of code should be briefly commented with the reasoning/business logic that is being exercised. Thanks & Regards, *Ben Johnson* Sr. IT Staffing Specialist Voice: 201 255 0319 Ext: 236 | Fax: 201 727 9296 Email: [email protected] || [email protected] Linked in: http://www.linkedin.com/in/Benjohnsons --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Embedded_C++_VC++" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.in/group/Embedded_C_VC?hl=en -~----------~----~----~----~------~----~------~--~---
