Selectionable needs a very practical test of [login to view URL] test should be written both on English and on Spanish [login to view URL] features we need for this test are these ones:
1.- All questions are multiple-choice, consisting of until 5 possible answers. Skill tests are focused on practical, not theoretical concepts.
2.- Only one choice may be correct for each question.
3.- Test designers may use options such as “All of the above” and/or “None of the above” as the fifth option. If it used, at least two questions per each 30 must have as the correct answer “All” and/or another two “None.”
4.- Tests should have at least 10 questions for each general skill level, for a total of 30 questions. Keep each skill level separate by numbering them sequentially (1-10 Basic, 11-20 Intermediate, 21-30 Advanced).
5.- Questions should be original, created by the test designer.
6.- Questions should not be more than 255 characters in length.
7.- Answers should not be more than 100 characters in length (per answer).
8.- Language: All test must be written in English and Spanish. Use American spelling conventions for English.
9.- Pictures & graphics & video & sound items:
a. Questions may use graphical/picture/sound/video content. At least 10 questions will have this help resources. This is good for including examples of code or for communicating complex concepts that are easier to convey by an image or graph.
b. There can only be one picture/video/sound per question.
c. If the question consists of text and pictures then the picture must always be 320 x 320 pixels in jpg or png format.
d. Picture file names must follow this naming convention: Test(testNumber)-Preg(QuestionNumber).jpg (or .png). Example: [login to view URL]
10.- Designers must highlight the correct answers when submitting the test. Mark them by changing the font color to green and making it bold. Only the correct answer should be marked this way.
*No Upfront Payments only Milestone Escrow
*Ready for NDA and an interview
*FREE: Bug Tracking On BugZilla Tool & Test Reports Coverage
TECHNIQUES:
*Data Migration testing
*API, Web Services testing
*Acceptance Testing
*Security testing
*Mobile and Website Browser Testing
*UX/UI Testing
TOOLS:
*Open Source
Bugzilla can be used as an opensource bug tracking tool
*Paid
JIRA from atlassian is a very good bug tracking tool. This can also be put in the kanban mode of agile development
ENVIRONMENTS
-Development Env.
-IIT Env. (Internal Integration testing Env.)
-Staging Env. (First QA Testing)
-CTE (Customer Testing Env) or LT (Live Testing Env.)
PROCESS
-Before testing on the QA env. The previously run env would be backed up
-The bug list would be provided by locking the bugs along with the severity status
-The next drop with the fixes would be tested again and env would be sanitized again
-The env would be rolled back as and when a new drops comes in
-Beta testing would be done with the end user therefore the person from our QA team would make the user understand about the release and test cases
RELEASE MANAGEMENT
-After the testing is complete each of the release would be given a unique number to identify the drop and the release made as a bug free product
-Release number and Change description through release notes would be maintained
-Bug report for specific release would be submitted to the client
DOCUMENT REPORTS
-Test Matrices
-Bug Report
-Test Coverage
Regard
Gopal