2.6.3 User Interface
Different Polls could be present at different channels,
pages within channels, and at home page. User interface for
Poll will be as described below:
- Beneath poll current result(running status) to be
shown in graphical form(say progressing bar chart) all the
time, in same window as poll.
- Link ""All Polls >>"" to take user to Polls home
page which will have all the active polls with results
underneath.
- All the polls not older than one month will come
under Active polls category.
- User can take Active open polls, but cannot react
to Active closed polls. Can only view results of active
closed polls.
- No Interactives available for polls - "Add a
comment", "Rate"
- Registered User can take a poll only once, after
that only result is shown to user. To unregistered user it
will be open.
2.6.4 Interfacing/Sourcing Details
- Polls is going to be a separate module, an internal
application, which editor/admin can publish.
- Admin/Editor should be able to publish polls on
separate channels, pages. Assign closure dates.
- Admin/Editor can upload images, change look n feel,
add a brand, link/url to it.
- System to capture user details(screen name/name,
id, email id), do loyalilty points calculation and add to
user loyality points.
2.6.5 Rules and Conditions
Unless assigned a closure date, by default all Polls will
be open for 30 days.
this is the SRS how to write the test cases for the above
functionalities help me
Re: 2.6.3 User Interface
Different Polls could be present at different channels,
pages within channels, and at home page. User interface for
Poll will be as described below:
- Beneath poll current result(running status) to be
shown in graphical form(say progressing bar chart) all the
time, in same window as poll.
- Link ""All Polls >>"" to take user to Polls home
page which will have all the active polls with results
underneath.
- All the polls not older than one month will come
under Active polls category.
- User can take Active open polls, but cannot react
to Active closed polls. Can only view results of active
closed polls.
- No Interactives available for polls - "Add a
comment", "Rate"
- Registered User can take a poll only once, after
that only result is shown to user. To unregistered user it
will be open.
2.6.4 Interfacing/Sourcing Details
- Polls is going to be a separate module, an internal
application, which editor/admin can publish.
- Admin/Editor should be able to publish polls on
separate channels, pages. Assign closure dates.
- Admin/Editor can upload images, change look n feel,
add a brand, link/url to it.
- System to capture user details(screen name/name,
id, email id), do loyalilty points calculation and add to
user loyality points.
2.6.5 Rules and Conditions
Unless assigned a closure date, by default all Polls will
be open for 30 days.
this is the SRS how to write the test cases for the above
functionalities help me
this is not single scenario man first design the test
scenarios then u can design the test cases easily
any how i am writing some scenarios with the test cases.
1> Different Polls could be present at different channels,
pages within channels, and at home page.?
scenario1: checking the different polls present in the home page
Scenario2: checking the different polls present in the
different channels
Scenario3: checking the different polls present in the xyz
channel page
if i have to write for all it takes more than this if needed
to write more please contact me on jagadishk.9454@gmail.com
(questions asked in interview)hi every one can any one
please answer to this questions.these questions were asked
in an interview.i have another interview next week . 1.when
the time schedule is tight how will you approch the
testing,and the relese is nearing and we need to finish
testing how can we follow in that case.do we need to exicute
all the test cases or can priortise and leave some to next
relase. 2. when a new feature is added to the existing
application we need to add new test cases but after that do
we need to change all the existing test cases and while
running do we need to exicute entire application test cases
or only the new feature test cases and related new feature
test cases. 3.do you have any situation where you have to
write and exicute the test cases same time, how will you
follow.does it happens in real time. 4.example of bug which
is not reproducible.like tester say that there is bug and
developer say no can some example of such bugs. 5.during
regression testing some times do we need to add new some
additional test cases to test that bug.
if u want to test an application which takes a data value
between 0 and 59 and if u choose 55 ,what type of testing
it is
a) System testing
b) error guessing
c) Black box
d) None
if account balance less than 5000 for a month ,account
should become in active. if bal greater than 5000 account
should b active. Write test cases for the above scenario
along with your userid / name. ThanQ
Site Map
